Backspace, Tab not working in terminal (using ssh)
Clash Royale CLAN TAG#URR8PPP
up vote
31
down vote
favorite
When I ssh into another machine with Debian with my account(with sudo permissions), my backspace key generates some awkward symbols on pressing. Also Tab & del keys don't work too.
On the other hand, I also have another account on the same machine & when I ssh through this account, its terminal works perfectly fine. I couldn't figure out why is this happening.
linux debian terminal
add a comment |
up vote
31
down vote
favorite
When I ssh into another machine with Debian with my account(with sudo permissions), my backspace key generates some awkward symbols on pressing. Also Tab & del keys don't work too.
On the other hand, I also have another account on the same machine & when I ssh through this account, its terminal works perfectly fine. I couldn't figure out why is this happening.
linux debian terminal
Could be a keyboard and text encoding issue, do they all use the same language and keyboard settings?
– Kevin
Jul 15 '12 at 11:36
@Kevin How to check for that?
– gopi1410
Jul 15 '12 at 11:58
Occasionally mine does it too. But mybackspace
is acting like my return (Enter) key. @gopi1410, you're not the only one with this issue +1 for the question!
– Kevdog777
Aug 14 '12 at 13:57
add a comment |
up vote
31
down vote
favorite
up vote
31
down vote
favorite
When I ssh into another machine with Debian with my account(with sudo permissions), my backspace key generates some awkward symbols on pressing. Also Tab & del keys don't work too.
On the other hand, I also have another account on the same machine & when I ssh through this account, its terminal works perfectly fine. I couldn't figure out why is this happening.
linux debian terminal
When I ssh into another machine with Debian with my account(with sudo permissions), my backspace key generates some awkward symbols on pressing. Also Tab & del keys don't work too.
On the other hand, I also have another account on the same machine & when I ssh through this account, its terminal works perfectly fine. I couldn't figure out why is this happening.
linux debian terminal
linux debian terminal
edited Dec 9 '16 at 8:39
Mongrel
2,04131344
2,04131344
asked Jul 15 '12 at 11:13
gopi1410
259135
259135
Could be a keyboard and text encoding issue, do they all use the same language and keyboard settings?
– Kevin
Jul 15 '12 at 11:36
@Kevin How to check for that?
– gopi1410
Jul 15 '12 at 11:58
Occasionally mine does it too. But mybackspace
is acting like my return (Enter) key. @gopi1410, you're not the only one with this issue +1 for the question!
– Kevdog777
Aug 14 '12 at 13:57
add a comment |
Could be a keyboard and text encoding issue, do they all use the same language and keyboard settings?
– Kevin
Jul 15 '12 at 11:36
@Kevin How to check for that?
– gopi1410
Jul 15 '12 at 11:58
Occasionally mine does it too. But mybackspace
is acting like my return (Enter) key. @gopi1410, you're not the only one with this issue +1 for the question!
– Kevdog777
Aug 14 '12 at 13:57
Could be a keyboard and text encoding issue, do they all use the same language and keyboard settings?
– Kevin
Jul 15 '12 at 11:36
Could be a keyboard and text encoding issue, do they all use the same language and keyboard settings?
– Kevin
Jul 15 '12 at 11:36
@Kevin How to check for that?
– gopi1410
Jul 15 '12 at 11:58
@Kevin How to check for that?
– gopi1410
Jul 15 '12 at 11:58
Occasionally mine does it too. But my
backspace
is acting like my return (Enter) key. @gopi1410, you're not the only one with this issue +1 for the question!– Kevdog777
Aug 14 '12 at 13:57
Occasionally mine does it too. But my
backspace
is acting like my return (Enter) key. @gopi1410, you're not the only one with this issue +1 for the question!– Kevdog777
Aug 14 '12 at 13:57
add a comment |
7 Answers
7
active
oldest
votes
up vote
30
down vote
I have seen such problems before.
Take the backspace for example, the remote host expects some character to be used as "erase/backspace" , while you pressing backspace in the terminal , the terminal program will send some character to the remote host, if what the remote host expects diffs with the characters sent by the terminal program, you would encounter this issue. So a quick fix is as below:
- run command
#stty -a
in the remote host, and find what is expected to be an erase code in the output. Sayerase=^?
. - In the terminal, type Ctrlv and press your backspace. You'll see what code is sent as "erase". Say it is
^H
. - In the remote host, run
#stty erase ^H
.
(Note: use Ctrlv + Backspace, do not type the ^ manually)
You can fix the Tab issue with the same as above.
My backspace character is some special symbol something like an inverted triangle. So its not working
– gopi1410
Jul 16 '12 at 10:26
1
This simple comment is certainly the best solution I have seen to this. It feels like a kludge but it works.
– Paulo Matos
Aug 13 '15 at 8:08
This worked for me! What I don't understand though is why my shell handles backspace as expected, but reading from stdin in my app does not. Doing your suggested change results in backspace working for both. My understanding is that the shell handles stdin buffering, so shouldn't the backspace-handling be the same for both the shell and an app?
– Samuel
Aug 18 '15 at 22:24
What if no code at all is sent? Ctrlv + backspace produces nothing...
– Manfredo
Jul 31 '17 at 8:24
add a comment |
up vote
19
down vote
Beside "stty" solution, you may try the "TERM" solution.
You ssh to your Debian from some terminal (putty, solaris dterm, debain xterm, you-name-it), this termninal announce capabilities (which includes keys such as Backspace and Tab) via TERM environment variable.
So, after ssh to unix host (it doesn't depend debian it or other host) set the TERM variable according to your terminal. Consider you're using bash as shell and vt100 as terminal:
export TERM=vt100
ps: TERM should be announced via ssh automagically, but in some circumstances this magic fails.
still doesn't work :(
– gopi1410
Aug 14 '12 at 17:49
What terminal are you using? And what the value of TERM you have tried?
– paul
Aug 15 '12 at 6:23
I tried vt100. How do I get to know the value of TERM? I tried ssh from cygwin (in windows) to Debian. If there are problems with cygwin, I even tried it from ubuntu terminal, but same problem.
– gopi1410
Aug 15 '12 at 12:30
Not sure cygwin has good terminal emulation, as far as I know, cygwin just using regular windows console which lacks terminal emulation (may be wrong). From ubuntu all should works just fine. Something wrong with shell or termcap library on debian. Login from Ubuntu and give me output of commands: 1. echo $TERM 2. stty -a
– paul
Aug 16 '12 at 4:13
Well it works fine from my ubuntu machine, wonder why I hadn't verified it before.($TERM was 'xterm' there). So the problem is with cygwin only. Well anyways problem solved if it works with ubuntu :)
– gopi1410
Aug 16 '12 at 6:35
|
show 1 more comment
up vote
9
down vote
This is because your default shell is sh
, to use bash, just run bash
from your shell.
bash
To set bash as your default shell:
chsh -s /bin/bash
or
sudo chsh -s /bin/bash yourusername
This one fixed it for me. Never even though to look at my login shell!
– James Pack
Jul 3 '17 at 17:19
add a comment |
up vote
7
down vote
Your shell may be set to /bin/sh
instead of /bin/bash
1
Related to this answer: unix.stackexchange.com/questions/50542/…
– Samuel
Sep 3 '15 at 18:36
1
cyberciti.biz/faq/howto-set-bash-as-your-default-shell
– teynon
Dec 16 '15 at 2:52
This would be more helpful if it explained a little more and how to change it, but it was the problem I had. Thanks @Tom for your link that fixed the issue for me.
– Jake
Mar 28 '16 at 14:40
add a comment |
up vote
4
down vote
I usually use this to fix any funky character output in my terminal. It resets all the special characters to their default values.
stty sane
From the stty man page:
same as cread -ignbrk brkint -inlcr -igncr icrnl -iutf8 -ixoff -iuclc -ixany imaxbel opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke, all special characters to their default values
Backspace is working but tab still fails.
– Udo
May 3 '17 at 7:12
add a comment |
up vote
1
down vote
on top of paul's answer, if you want to retain the ability to have colorful output, you can use xterm-88color
echo 'export TERM=xterm-88color' >> ~/.bashrc
source ~/.bashrc
add a comment |
up vote
0
down vote
# stty -a
speed 38400 baud; rows 34; columns 134; line = 0;
intr = ^C; quit = ^; erase = ^H; kill = ^U; eof = ^D; eol = <undef>; eol2 =
<undef>; swtch = <undef>; start = ^Q; stop = ^S;
susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts
-ignbrk brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -
iuclc -ixany imaxbel -iutf8
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl
echoke
My home key prints a ^[[1~, as per @Derui Si's solution my backspace key is working fine not sure what to do for home key.
add a comment |
7 Answers
7
active
oldest
votes
7 Answers
7
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
30
down vote
I have seen such problems before.
Take the backspace for example, the remote host expects some character to be used as "erase/backspace" , while you pressing backspace in the terminal , the terminal program will send some character to the remote host, if what the remote host expects diffs with the characters sent by the terminal program, you would encounter this issue. So a quick fix is as below:
- run command
#stty -a
in the remote host, and find what is expected to be an erase code in the output. Sayerase=^?
. - In the terminal, type Ctrlv and press your backspace. You'll see what code is sent as "erase". Say it is
^H
. - In the remote host, run
#stty erase ^H
.
(Note: use Ctrlv + Backspace, do not type the ^ manually)
You can fix the Tab issue with the same as above.
My backspace character is some special symbol something like an inverted triangle. So its not working
– gopi1410
Jul 16 '12 at 10:26
1
This simple comment is certainly the best solution I have seen to this. It feels like a kludge but it works.
– Paulo Matos
Aug 13 '15 at 8:08
This worked for me! What I don't understand though is why my shell handles backspace as expected, but reading from stdin in my app does not. Doing your suggested change results in backspace working for both. My understanding is that the shell handles stdin buffering, so shouldn't the backspace-handling be the same for both the shell and an app?
– Samuel
Aug 18 '15 at 22:24
What if no code at all is sent? Ctrlv + backspace produces nothing...
– Manfredo
Jul 31 '17 at 8:24
add a comment |
up vote
30
down vote
I have seen such problems before.
Take the backspace for example, the remote host expects some character to be used as "erase/backspace" , while you pressing backspace in the terminal , the terminal program will send some character to the remote host, if what the remote host expects diffs with the characters sent by the terminal program, you would encounter this issue. So a quick fix is as below:
- run command
#stty -a
in the remote host, and find what is expected to be an erase code in the output. Sayerase=^?
. - In the terminal, type Ctrlv and press your backspace. You'll see what code is sent as "erase". Say it is
^H
. - In the remote host, run
#stty erase ^H
.
(Note: use Ctrlv + Backspace, do not type the ^ manually)
You can fix the Tab issue with the same as above.
My backspace character is some special symbol something like an inverted triangle. So its not working
– gopi1410
Jul 16 '12 at 10:26
1
This simple comment is certainly the best solution I have seen to this. It feels like a kludge but it works.
– Paulo Matos
Aug 13 '15 at 8:08
This worked for me! What I don't understand though is why my shell handles backspace as expected, but reading from stdin in my app does not. Doing your suggested change results in backspace working for both. My understanding is that the shell handles stdin buffering, so shouldn't the backspace-handling be the same for both the shell and an app?
– Samuel
Aug 18 '15 at 22:24
What if no code at all is sent? Ctrlv + backspace produces nothing...
– Manfredo
Jul 31 '17 at 8:24
add a comment |
up vote
30
down vote
up vote
30
down vote
I have seen such problems before.
Take the backspace for example, the remote host expects some character to be used as "erase/backspace" , while you pressing backspace in the terminal , the terminal program will send some character to the remote host, if what the remote host expects diffs with the characters sent by the terminal program, you would encounter this issue. So a quick fix is as below:
- run command
#stty -a
in the remote host, and find what is expected to be an erase code in the output. Sayerase=^?
. - In the terminal, type Ctrlv and press your backspace. You'll see what code is sent as "erase". Say it is
^H
. - In the remote host, run
#stty erase ^H
.
(Note: use Ctrlv + Backspace, do not type the ^ manually)
You can fix the Tab issue with the same as above.
I have seen such problems before.
Take the backspace for example, the remote host expects some character to be used as "erase/backspace" , while you pressing backspace in the terminal , the terminal program will send some character to the remote host, if what the remote host expects diffs with the characters sent by the terminal program, you would encounter this issue. So a quick fix is as below:
- run command
#stty -a
in the remote host, and find what is expected to be an erase code in the output. Sayerase=^?
. - In the terminal, type Ctrlv and press your backspace. You'll see what code is sent as "erase". Say it is
^H
. - In the remote host, run
#stty erase ^H
.
(Note: use Ctrlv + Backspace, do not type the ^ manually)
You can fix the Tab issue with the same as above.
edited Jan 12 '16 at 14:20
aweibell
1033
1033
answered Jul 15 '12 at 13:10
Derui Si
44944
44944
My backspace character is some special symbol something like an inverted triangle. So its not working
– gopi1410
Jul 16 '12 at 10:26
1
This simple comment is certainly the best solution I have seen to this. It feels like a kludge but it works.
– Paulo Matos
Aug 13 '15 at 8:08
This worked for me! What I don't understand though is why my shell handles backspace as expected, but reading from stdin in my app does not. Doing your suggested change results in backspace working for both. My understanding is that the shell handles stdin buffering, so shouldn't the backspace-handling be the same for both the shell and an app?
– Samuel
Aug 18 '15 at 22:24
What if no code at all is sent? Ctrlv + backspace produces nothing...
– Manfredo
Jul 31 '17 at 8:24
add a comment |
My backspace character is some special symbol something like an inverted triangle. So its not working
– gopi1410
Jul 16 '12 at 10:26
1
This simple comment is certainly the best solution I have seen to this. It feels like a kludge but it works.
– Paulo Matos
Aug 13 '15 at 8:08
This worked for me! What I don't understand though is why my shell handles backspace as expected, but reading from stdin in my app does not. Doing your suggested change results in backspace working for both. My understanding is that the shell handles stdin buffering, so shouldn't the backspace-handling be the same for both the shell and an app?
– Samuel
Aug 18 '15 at 22:24
What if no code at all is sent? Ctrlv + backspace produces nothing...
– Manfredo
Jul 31 '17 at 8:24
My backspace character is some special symbol something like an inverted triangle. So its not working
– gopi1410
Jul 16 '12 at 10:26
My backspace character is some special symbol something like an inverted triangle. So its not working
– gopi1410
Jul 16 '12 at 10:26
1
1
This simple comment is certainly the best solution I have seen to this. It feels like a kludge but it works.
– Paulo Matos
Aug 13 '15 at 8:08
This simple comment is certainly the best solution I have seen to this. It feels like a kludge but it works.
– Paulo Matos
Aug 13 '15 at 8:08
This worked for me! What I don't understand though is why my shell handles backspace as expected, but reading from stdin in my app does not. Doing your suggested change results in backspace working for both. My understanding is that the shell handles stdin buffering, so shouldn't the backspace-handling be the same for both the shell and an app?
– Samuel
Aug 18 '15 at 22:24
This worked for me! What I don't understand though is why my shell handles backspace as expected, but reading from stdin in my app does not. Doing your suggested change results in backspace working for both. My understanding is that the shell handles stdin buffering, so shouldn't the backspace-handling be the same for both the shell and an app?
– Samuel
Aug 18 '15 at 22:24
What if no code at all is sent? Ctrlv + backspace produces nothing...
– Manfredo
Jul 31 '17 at 8:24
What if no code at all is sent? Ctrlv + backspace produces nothing...
– Manfredo
Jul 31 '17 at 8:24
add a comment |
up vote
19
down vote
Beside "stty" solution, you may try the "TERM" solution.
You ssh to your Debian from some terminal (putty, solaris dterm, debain xterm, you-name-it), this termninal announce capabilities (which includes keys such as Backspace and Tab) via TERM environment variable.
So, after ssh to unix host (it doesn't depend debian it or other host) set the TERM variable according to your terminal. Consider you're using bash as shell and vt100 as terminal:
export TERM=vt100
ps: TERM should be announced via ssh automagically, but in some circumstances this magic fails.
still doesn't work :(
– gopi1410
Aug 14 '12 at 17:49
What terminal are you using? And what the value of TERM you have tried?
– paul
Aug 15 '12 at 6:23
I tried vt100. How do I get to know the value of TERM? I tried ssh from cygwin (in windows) to Debian. If there are problems with cygwin, I even tried it from ubuntu terminal, but same problem.
– gopi1410
Aug 15 '12 at 12:30
Not sure cygwin has good terminal emulation, as far as I know, cygwin just using regular windows console which lacks terminal emulation (may be wrong). From ubuntu all should works just fine. Something wrong with shell or termcap library on debian. Login from Ubuntu and give me output of commands: 1. echo $TERM 2. stty -a
– paul
Aug 16 '12 at 4:13
Well it works fine from my ubuntu machine, wonder why I hadn't verified it before.($TERM was 'xterm' there). So the problem is with cygwin only. Well anyways problem solved if it works with ubuntu :)
– gopi1410
Aug 16 '12 at 6:35
|
show 1 more comment
up vote
19
down vote
Beside "stty" solution, you may try the "TERM" solution.
You ssh to your Debian from some terminal (putty, solaris dterm, debain xterm, you-name-it), this termninal announce capabilities (which includes keys such as Backspace and Tab) via TERM environment variable.
So, after ssh to unix host (it doesn't depend debian it or other host) set the TERM variable according to your terminal. Consider you're using bash as shell and vt100 as terminal:
export TERM=vt100
ps: TERM should be announced via ssh automagically, but in some circumstances this magic fails.
still doesn't work :(
– gopi1410
Aug 14 '12 at 17:49
What terminal are you using? And what the value of TERM you have tried?
– paul
Aug 15 '12 at 6:23
I tried vt100. How do I get to know the value of TERM? I tried ssh from cygwin (in windows) to Debian. If there are problems with cygwin, I even tried it from ubuntu terminal, but same problem.
– gopi1410
Aug 15 '12 at 12:30
Not sure cygwin has good terminal emulation, as far as I know, cygwin just using regular windows console which lacks terminal emulation (may be wrong). From ubuntu all should works just fine. Something wrong with shell or termcap library on debian. Login from Ubuntu and give me output of commands: 1. echo $TERM 2. stty -a
– paul
Aug 16 '12 at 4:13
Well it works fine from my ubuntu machine, wonder why I hadn't verified it before.($TERM was 'xterm' there). So the problem is with cygwin only. Well anyways problem solved if it works with ubuntu :)
– gopi1410
Aug 16 '12 at 6:35
|
show 1 more comment
up vote
19
down vote
up vote
19
down vote
Beside "stty" solution, you may try the "TERM" solution.
You ssh to your Debian from some terminal (putty, solaris dterm, debain xterm, you-name-it), this termninal announce capabilities (which includes keys such as Backspace and Tab) via TERM environment variable.
So, after ssh to unix host (it doesn't depend debian it or other host) set the TERM variable according to your terminal. Consider you're using bash as shell and vt100 as terminal:
export TERM=vt100
ps: TERM should be announced via ssh automagically, but in some circumstances this magic fails.
Beside "stty" solution, you may try the "TERM" solution.
You ssh to your Debian from some terminal (putty, solaris dterm, debain xterm, you-name-it), this termninal announce capabilities (which includes keys such as Backspace and Tab) via TERM environment variable.
So, after ssh to unix host (it doesn't depend debian it or other host) set the TERM variable according to your terminal. Consider you're using bash as shell and vt100 as terminal:
export TERM=vt100
ps: TERM should be announced via ssh automagically, but in some circumstances this magic fails.
answered Aug 14 '12 at 14:56
paul
1,117167
1,117167
still doesn't work :(
– gopi1410
Aug 14 '12 at 17:49
What terminal are you using? And what the value of TERM you have tried?
– paul
Aug 15 '12 at 6:23
I tried vt100. How do I get to know the value of TERM? I tried ssh from cygwin (in windows) to Debian. If there are problems with cygwin, I even tried it from ubuntu terminal, but same problem.
– gopi1410
Aug 15 '12 at 12:30
Not sure cygwin has good terminal emulation, as far as I know, cygwin just using regular windows console which lacks terminal emulation (may be wrong). From ubuntu all should works just fine. Something wrong with shell or termcap library on debian. Login from Ubuntu and give me output of commands: 1. echo $TERM 2. stty -a
– paul
Aug 16 '12 at 4:13
Well it works fine from my ubuntu machine, wonder why I hadn't verified it before.($TERM was 'xterm' there). So the problem is with cygwin only. Well anyways problem solved if it works with ubuntu :)
– gopi1410
Aug 16 '12 at 6:35
|
show 1 more comment
still doesn't work :(
– gopi1410
Aug 14 '12 at 17:49
What terminal are you using? And what the value of TERM you have tried?
– paul
Aug 15 '12 at 6:23
I tried vt100. How do I get to know the value of TERM? I tried ssh from cygwin (in windows) to Debian. If there are problems with cygwin, I even tried it from ubuntu terminal, but same problem.
– gopi1410
Aug 15 '12 at 12:30
Not sure cygwin has good terminal emulation, as far as I know, cygwin just using regular windows console which lacks terminal emulation (may be wrong). From ubuntu all should works just fine. Something wrong with shell or termcap library on debian. Login from Ubuntu and give me output of commands: 1. echo $TERM 2. stty -a
– paul
Aug 16 '12 at 4:13
Well it works fine from my ubuntu machine, wonder why I hadn't verified it before.($TERM was 'xterm' there). So the problem is with cygwin only. Well anyways problem solved if it works with ubuntu :)
– gopi1410
Aug 16 '12 at 6:35
still doesn't work :(
– gopi1410
Aug 14 '12 at 17:49
still doesn't work :(
– gopi1410
Aug 14 '12 at 17:49
What terminal are you using? And what the value of TERM you have tried?
– paul
Aug 15 '12 at 6:23
What terminal are you using? And what the value of TERM you have tried?
– paul
Aug 15 '12 at 6:23
I tried vt100. How do I get to know the value of TERM? I tried ssh from cygwin (in windows) to Debian. If there are problems with cygwin, I even tried it from ubuntu terminal, but same problem.
– gopi1410
Aug 15 '12 at 12:30
I tried vt100. How do I get to know the value of TERM? I tried ssh from cygwin (in windows) to Debian. If there are problems with cygwin, I even tried it from ubuntu terminal, but same problem.
– gopi1410
Aug 15 '12 at 12:30
Not sure cygwin has good terminal emulation, as far as I know, cygwin just using regular windows console which lacks terminal emulation (may be wrong). From ubuntu all should works just fine. Something wrong with shell or termcap library on debian. Login from Ubuntu and give me output of commands: 1. echo $TERM 2. stty -a
– paul
Aug 16 '12 at 4:13
Not sure cygwin has good terminal emulation, as far as I know, cygwin just using regular windows console which lacks terminal emulation (may be wrong). From ubuntu all should works just fine. Something wrong with shell or termcap library on debian. Login from Ubuntu and give me output of commands: 1. echo $TERM 2. stty -a
– paul
Aug 16 '12 at 4:13
Well it works fine from my ubuntu machine, wonder why I hadn't verified it before.($TERM was 'xterm' there). So the problem is with cygwin only. Well anyways problem solved if it works with ubuntu :)
– gopi1410
Aug 16 '12 at 6:35
Well it works fine from my ubuntu machine, wonder why I hadn't verified it before.($TERM was 'xterm' there). So the problem is with cygwin only. Well anyways problem solved if it works with ubuntu :)
– gopi1410
Aug 16 '12 at 6:35
|
show 1 more comment
up vote
9
down vote
This is because your default shell is sh
, to use bash, just run bash
from your shell.
bash
To set bash as your default shell:
chsh -s /bin/bash
or
sudo chsh -s /bin/bash yourusername
This one fixed it for me. Never even though to look at my login shell!
– James Pack
Jul 3 '17 at 17:19
add a comment |
up vote
9
down vote
This is because your default shell is sh
, to use bash, just run bash
from your shell.
bash
To set bash as your default shell:
chsh -s /bin/bash
or
sudo chsh -s /bin/bash yourusername
This one fixed it for me. Never even though to look at my login shell!
– James Pack
Jul 3 '17 at 17:19
add a comment |
up vote
9
down vote
up vote
9
down vote
This is because your default shell is sh
, to use bash, just run bash
from your shell.
bash
To set bash as your default shell:
chsh -s /bin/bash
or
sudo chsh -s /bin/bash yourusername
This is because your default shell is sh
, to use bash, just run bash
from your shell.
bash
To set bash as your default shell:
chsh -s /bin/bash
or
sudo chsh -s /bin/bash yourusername
edited Jun 14 '16 at 10:26
Anthony Geoghegan
7,41033854
7,41033854
answered Jun 14 '16 at 10:08
iceflame
9113
9113
This one fixed it for me. Never even though to look at my login shell!
– James Pack
Jul 3 '17 at 17:19
add a comment |
This one fixed it for me. Never even though to look at my login shell!
– James Pack
Jul 3 '17 at 17:19
This one fixed it for me. Never even though to look at my login shell!
– James Pack
Jul 3 '17 at 17:19
This one fixed it for me. Never even though to look at my login shell!
– James Pack
Jul 3 '17 at 17:19
add a comment |
up vote
7
down vote
Your shell may be set to /bin/sh
instead of /bin/bash
1
Related to this answer: unix.stackexchange.com/questions/50542/…
– Samuel
Sep 3 '15 at 18:36
1
cyberciti.biz/faq/howto-set-bash-as-your-default-shell
– teynon
Dec 16 '15 at 2:52
This would be more helpful if it explained a little more and how to change it, but it was the problem I had. Thanks @Tom for your link that fixed the issue for me.
– Jake
Mar 28 '16 at 14:40
add a comment |
up vote
7
down vote
Your shell may be set to /bin/sh
instead of /bin/bash
1
Related to this answer: unix.stackexchange.com/questions/50542/…
– Samuel
Sep 3 '15 at 18:36
1
cyberciti.biz/faq/howto-set-bash-as-your-default-shell
– teynon
Dec 16 '15 at 2:52
This would be more helpful if it explained a little more and how to change it, but it was the problem I had. Thanks @Tom for your link that fixed the issue for me.
– Jake
Mar 28 '16 at 14:40
add a comment |
up vote
7
down vote
up vote
7
down vote
Your shell may be set to /bin/sh
instead of /bin/bash
Your shell may be set to /bin/sh
instead of /bin/bash
edited Jul 30 '13 at 5:03
Anthon
59.6k17101162
59.6k17101162
answered Jul 30 '13 at 4:45
jm.
17113
17113
1
Related to this answer: unix.stackexchange.com/questions/50542/…
– Samuel
Sep 3 '15 at 18:36
1
cyberciti.biz/faq/howto-set-bash-as-your-default-shell
– teynon
Dec 16 '15 at 2:52
This would be more helpful if it explained a little more and how to change it, but it was the problem I had. Thanks @Tom for your link that fixed the issue for me.
– Jake
Mar 28 '16 at 14:40
add a comment |
1
Related to this answer: unix.stackexchange.com/questions/50542/…
– Samuel
Sep 3 '15 at 18:36
1
cyberciti.biz/faq/howto-set-bash-as-your-default-shell
– teynon
Dec 16 '15 at 2:52
This would be more helpful if it explained a little more and how to change it, but it was the problem I had. Thanks @Tom for your link that fixed the issue for me.
– Jake
Mar 28 '16 at 14:40
1
1
Related to this answer: unix.stackexchange.com/questions/50542/…
– Samuel
Sep 3 '15 at 18:36
Related to this answer: unix.stackexchange.com/questions/50542/…
– Samuel
Sep 3 '15 at 18:36
1
1
cyberciti.biz/faq/howto-set-bash-as-your-default-shell
– teynon
Dec 16 '15 at 2:52
cyberciti.biz/faq/howto-set-bash-as-your-default-shell
– teynon
Dec 16 '15 at 2:52
This would be more helpful if it explained a little more and how to change it, but it was the problem I had. Thanks @Tom for your link that fixed the issue for me.
– Jake
Mar 28 '16 at 14:40
This would be more helpful if it explained a little more and how to change it, but it was the problem I had. Thanks @Tom for your link that fixed the issue for me.
– Jake
Mar 28 '16 at 14:40
add a comment |
up vote
4
down vote
I usually use this to fix any funky character output in my terminal. It resets all the special characters to their default values.
stty sane
From the stty man page:
same as cread -ignbrk brkint -inlcr -igncr icrnl -iutf8 -ixoff -iuclc -ixany imaxbel opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke, all special characters to their default values
Backspace is working but tab still fails.
– Udo
May 3 '17 at 7:12
add a comment |
up vote
4
down vote
I usually use this to fix any funky character output in my terminal. It resets all the special characters to their default values.
stty sane
From the stty man page:
same as cread -ignbrk brkint -inlcr -igncr icrnl -iutf8 -ixoff -iuclc -ixany imaxbel opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke, all special characters to their default values
Backspace is working but tab still fails.
– Udo
May 3 '17 at 7:12
add a comment |
up vote
4
down vote
up vote
4
down vote
I usually use this to fix any funky character output in my terminal. It resets all the special characters to their default values.
stty sane
From the stty man page:
same as cread -ignbrk brkint -inlcr -igncr icrnl -iutf8 -ixoff -iuclc -ixany imaxbel opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke, all special characters to their default values
I usually use this to fix any funky character output in my terminal. It resets all the special characters to their default values.
stty sane
From the stty man page:
same as cread -ignbrk brkint -inlcr -igncr icrnl -iutf8 -ixoff -iuclc -ixany imaxbel opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke, all special characters to their default values
answered Dec 1 '16 at 20:56
David Morales
1412
1412
Backspace is working but tab still fails.
– Udo
May 3 '17 at 7:12
add a comment |
Backspace is working but tab still fails.
– Udo
May 3 '17 at 7:12
Backspace is working but tab still fails.
– Udo
May 3 '17 at 7:12
Backspace is working but tab still fails.
– Udo
May 3 '17 at 7:12
add a comment |
up vote
1
down vote
on top of paul's answer, if you want to retain the ability to have colorful output, you can use xterm-88color
echo 'export TERM=xterm-88color' >> ~/.bashrc
source ~/.bashrc
add a comment |
up vote
1
down vote
on top of paul's answer, if you want to retain the ability to have colorful output, you can use xterm-88color
echo 'export TERM=xterm-88color' >> ~/.bashrc
source ~/.bashrc
add a comment |
up vote
1
down vote
up vote
1
down vote
on top of paul's answer, if you want to retain the ability to have colorful output, you can use xterm-88color
echo 'export TERM=xterm-88color' >> ~/.bashrc
source ~/.bashrc
on top of paul's answer, if you want to retain the ability to have colorful output, you can use xterm-88color
echo 'export TERM=xterm-88color' >> ~/.bashrc
source ~/.bashrc
answered Apr 10 at 4:09
beenotung
133
133
add a comment |
add a comment |
up vote
0
down vote
# stty -a
speed 38400 baud; rows 34; columns 134; line = 0;
intr = ^C; quit = ^; erase = ^H; kill = ^U; eof = ^D; eol = <undef>; eol2 =
<undef>; swtch = <undef>; start = ^Q; stop = ^S;
susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts
-ignbrk brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -
iuclc -ixany imaxbel -iutf8
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl
echoke
My home key prints a ^[[1~, as per @Derui Si's solution my backspace key is working fine not sure what to do for home key.
add a comment |
up vote
0
down vote
# stty -a
speed 38400 baud; rows 34; columns 134; line = 0;
intr = ^C; quit = ^; erase = ^H; kill = ^U; eof = ^D; eol = <undef>; eol2 =
<undef>; swtch = <undef>; start = ^Q; stop = ^S;
susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts
-ignbrk brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -
iuclc -ixany imaxbel -iutf8
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl
echoke
My home key prints a ^[[1~, as per @Derui Si's solution my backspace key is working fine not sure what to do for home key.
add a comment |
up vote
0
down vote
up vote
0
down vote
# stty -a
speed 38400 baud; rows 34; columns 134; line = 0;
intr = ^C; quit = ^; erase = ^H; kill = ^U; eof = ^D; eol = <undef>; eol2 =
<undef>; swtch = <undef>; start = ^Q; stop = ^S;
susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts
-ignbrk brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -
iuclc -ixany imaxbel -iutf8
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl
echoke
My home key prints a ^[[1~, as per @Derui Si's solution my backspace key is working fine not sure what to do for home key.
# stty -a
speed 38400 baud; rows 34; columns 134; line = 0;
intr = ^C; quit = ^; erase = ^H; kill = ^U; eof = ^D; eol = <undef>; eol2 =
<undef>; swtch = <undef>; start = ^Q; stop = ^S;
susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts
-ignbrk brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -
iuclc -ixany imaxbel -iutf8
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl
echoke
My home key prints a ^[[1~, as per @Derui Si's solution my backspace key is working fine not sure what to do for home key.
answered 2 days ago
Aditya
41
41
add a comment |
add a comment |
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%2funix.stackexchange.com%2fquestions%2f43103%2fbackspace-tab-not-working-in-terminal-using-ssh%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
Could be a keyboard and text encoding issue, do they all use the same language and keyboard settings?
– Kevin
Jul 15 '12 at 11:36
@Kevin How to check for that?
– gopi1410
Jul 15 '12 at 11:58
Occasionally mine does it too. But my
backspace
is acting like my return (Enter) key. @gopi1410, you're not the only one with this issue +1 for the question!– Kevdog777
Aug 14 '12 at 13:57