Change in arrow key behaviour under a GNU screen session
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I have noticed a weird behavior in GNU screen session while using arrow keys. I'm sure it is caused because of a change in setting/configuration. I'm looking here for the root cause of it.
Problem caused: Whenever, I want to switch to view the list of the bash sessions in attached screen using arrow keys, I couldn't. I had to use number keys to move to different bash sessions. Also, while using VIM, I couldn't traverse using arrow keys.
Problem solution: I could fixed it using the reset command for GNU screen session I had.
However, I'm still not sure what caused the issue.
gnu-screen
asked Feb 7 at 19:00
GC 13
419212
add a comment |Â
up vote
1
down vote
favorite
I have noticed a weird behavior in GNU screen session while using arrow keys. I'm sure it is caused because of a change in setting/configuration. I'm looking here for the root cause of it.
Problem caused: Whenever, I want to switch to view the list of the bash sessions in attached screen using arrow keys, I couldn't. I had to use number keys to move to different bash sessions. Also, while using VIM, I couldn't traverse using arrow keys.
Problem solution: I could fixed it using the reset command for GNU screen session I had.
However, I'm still not sure what caused the issue.
gnu-screen
asked Feb 7 at 19:00
GC 13
419212
1
check the TERM settings in your shell, and in the screen tabs. If your terminal is being set to VT-100, or a terminal that doesn't interpret the arrow keys as arrows, that could be the culprit. Or it may be that screen is trying to set TERM toscreen, but you don't have the screen termcap installed. Try runningscreen -T xtermand see if you get the expected behavior.
– Tim Kennedy
Feb 7 at 19:04
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have noticed a weird behavior in GNU screen session while using arrow keys. I'm sure it is caused because of a change in setting/configuration. I'm looking here for the root cause of it.
Problem caused: Whenever, I want to switch to view the list of the bash sessions in attached screen using arrow keys, I couldn't. I had to use number keys to move to different bash sessions. Also, while using VIM, I couldn't traverse using arrow keys.
Problem solution: I could fixed it using the reset command for GNU screen session I had.
However, I'm still not sure what caused the issue.
gnu-screen
asked Feb 7 at 19:00
GC 13
419212
I have noticed a weird behavior in GNU screen session while using arrow keys. I'm sure it is caused because of a change in setting/configuration. I'm looking here for the root cause of it.
Problem caused: Whenever, I want to switch to view the list of the bash sessions in attached screen using arrow keys, I couldn't. I had to use number keys to move to different bash sessions. Also, while using VIM, I couldn't traverse using arrow keys.
Problem solution: I could fixed it using the reset command for GNU screen session I had.
However, I'm still not sure what caused the issue.
gnu-screen
asked Feb 7 at 19:00
GC 13
419212
asked Feb 7 at 19:00
GC 13
419212
asked Feb 7 at 19:00
GC 13
419212
asked Feb 7 at 19:00
GC 13
419212
419212
1
check the TERM settings in your shell, and in the screen tabs. If your terminal is being set to VT-100, or a terminal that doesn't interpret the arrow keys as arrows, that could be the culprit. Or it may be that screen is trying to set TERM toscreen, but you don't have the screen termcap installed. Try runningscreen -T xtermand see if you get the expected behavior.
– Tim Kennedy
Feb 7 at 19:04
add a comment |Â
1
check the TERM settings in your shell, and in the screen tabs. If your terminal is being set to VT-100, or a terminal that doesn't interpret the arrow keys as arrows, that could be the culprit. Or it may be that screen is trying to set TERM toscreen, but you don't have the screen termcap installed. Try runningscreen -T xtermand see if you get the expected behavior.
– Tim Kennedy
Feb 7 at 19:04
1
1
check the TERM settings in your shell, and in the screen tabs. If your terminal is being set to VT-100, or a terminal that doesn't interpret the arrow keys as arrows, that could be the culprit. Or it may be that screen is trying to set TERM to
screen, but you don't have the screen termcap installed. Try running screen -T xterm and see if you get the expected behavior.– Tim Kennedy
Feb 7 at 19:04
check the TERM settings in your shell, and in the screen tabs. If your terminal is being set to VT-100, or a terminal that doesn't interpret the arrow keys as arrows, that could be the culprit. Or it may be that screen is trying to set TERM to
screen, but you don't have the screen termcap installed. Try running screen -T xterm and see if you get the expected behavior.– Tim Kennedy
Feb 7 at 19:04
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f422627%2fchange-in-arrow-key-behaviour-under-a-gnu-screen-session%23new-answer', 'question_page');
);
Post as a guest
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
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
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
1
check the TERM settings in your shell, and in the screen tabs. If your terminal is being set to VT-100, or a terminal that doesn't interpret the arrow keys as arrows, that could be the culprit. Or it may be that screen is trying to set TERM to
screen, but you don't have the screen termcap installed. Try runningscreen -T xtermand see if you get the expected behavior.– Tim Kennedy
Feb 7 at 19:04