Ctrl+b appearing as '^B' at command line
up vote
0
down vote
favorite
I noticed this behavior in tmux, but it also happens when I have no session attached. Instead of entering as the command key binding Ctrl+b, ^B is printed to the command line. I don't have a .tmux.config file. I am using iterm2 with zsh. Not sure what is going on... any help appreciated!
zsh tmux iterm2
asked Nov 29 at 6:32
Jeff Groh
11
add a comment |
up vote
0
down vote
favorite
I noticed this behavior in tmux, but it also happens when I have no session attached. Instead of entering as the command key binding Ctrl+b, ^B is printed to the command line. I don't have a .tmux.config file. I am using iterm2 with zsh. Not sure what is going on... any help appreciated!
zsh tmux iterm2
asked Nov 29 at 6:32
Jeff Groh
11
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I noticed this behavior in tmux, but it also happens when I have no session attached. Instead of entering as the command key binding Ctrl+b, ^B is printed to the command line. I don't have a .tmux.config file. I am using iterm2 with zsh. Not sure what is going on... any help appreciated!
zsh tmux iterm2
asked Nov 29 at 6:32
Jeff Groh
11
I noticed this behavior in tmux, but it also happens when I have no session attached. Instead of entering as the command key binding Ctrl+b, ^B is printed to the command line. I don't have a .tmux.config file. I am using iterm2 with zsh. Not sure what is going on... any help appreciated!
zsh tmux iterm2
zsh tmux iterm2
asked Nov 29 at 6:32
Jeff Groh
11
asked Nov 29 at 6:32
Jeff Groh
11
asked Nov 29 at 6:32
Jeff Groh
11
asked Nov 29 at 6:32
Jeff Groh
11
asked Nov 29 at 6:32
Jeff Groh
11
11
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
The shell is interpreting the Ctrl-B as input because it has no special meaning as your shell is currently configured. Most likely, your shell is set up to use vi style key bindings or are using non-standard key bindings.
The ^B you're getting is what's known as caret notation, and is the de-facto standard in most UNIX applications for representing control codes in a textual form. Wikipedia has a somewhat terse but still informative page on caret notation that may be of interest to you. You can produce similar results with most letters and a handful of other characters by hitting Ctrl-V prior to entering the desired key sequence (Ctrl-V tells the shell to treat the next byte of input as a literal value instead of a hotkey).
answered Nov 29 at 20:33
Austin Hemmelgarn
2,45918
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
The shell is interpreting the Ctrl-B as input because it has no special meaning as your shell is currently configured. Most likely, your shell is set up to use vi style key bindings or are using non-standard key bindings.
The ^B you're getting is what's known as caret notation, and is the de-facto standard in most UNIX applications for representing control codes in a textual form. Wikipedia has a somewhat terse but still informative page on caret notation that may be of interest to you. You can produce similar results with most letters and a handful of other characters by hitting Ctrl-V prior to entering the desired key sequence (Ctrl-V tells the shell to treat the next byte of input as a literal value instead of a hotkey).
answered Nov 29 at 20:33
Austin Hemmelgarn
2,45918
add a comment |
up vote
0
down vote
The shell is interpreting the Ctrl-B as input because it has no special meaning as your shell is currently configured. Most likely, your shell is set up to use vi style key bindings or are using non-standard key bindings.
The ^B you're getting is what's known as caret notation, and is the de-facto standard in most UNIX applications for representing control codes in a textual form. Wikipedia has a somewhat terse but still informative page on caret notation that may be of interest to you. You can produce similar results with most letters and a handful of other characters by hitting Ctrl-V prior to entering the desired key sequence (Ctrl-V tells the shell to treat the next byte of input as a literal value instead of a hotkey).
answered Nov 29 at 20:33
Austin Hemmelgarn
2,45918
add a comment |
up vote
0
down vote
up vote
0
down vote
The shell is interpreting the Ctrl-B as input because it has no special meaning as your shell is currently configured. Most likely, your shell is set up to use vi style key bindings or are using non-standard key bindings.
The ^B you're getting is what's known as caret notation, and is the de-facto standard in most UNIX applications for representing control codes in a textual form. Wikipedia has a somewhat terse but still informative page on caret notation that may be of interest to you. You can produce similar results with most letters and a handful of other characters by hitting Ctrl-V prior to entering the desired key sequence (Ctrl-V tells the shell to treat the next byte of input as a literal value instead of a hotkey).
answered Nov 29 at 20:33
Austin Hemmelgarn
2,45918
The shell is interpreting the Ctrl-B as input because it has no special meaning as your shell is currently configured. Most likely, your shell is set up to use vi style key bindings or are using non-standard key bindings.
The ^B you're getting is what's known as caret notation, and is the de-facto standard in most UNIX applications for representing control codes in a textual form. Wikipedia has a somewhat terse but still informative page on caret notation that may be of interest to you. You can produce similar results with most letters and a handful of other characters by hitting Ctrl-V prior to entering the desired key sequence (Ctrl-V tells the shell to treat the next byte of input as a literal value instead of a hotkey).
answered Nov 29 at 20:33
Austin Hemmelgarn
2,45918
answered Nov 29 at 20:33
Austin Hemmelgarn
2,45918
answered Nov 29 at 20:33
Austin Hemmelgarn
2,45918
answered Nov 29 at 20:33
Austin Hemmelgarn
2,45918
2,45918
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1379294%2fctrlb-appearing-as-b-at-command-line%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
