[SOLVED] Why any character can't be input at the back of . (dot character)in my bash?

luofeiyu · 07-19-2017, 10:17 PM

It is stragne that any character can't be input at the back of . (dot character)in my bash .
I want to check my .bashrc with the command `cat .bashrc`.
Once the `cat .` was inputted, to input `b` will result in many undesired output.
Is there an virus in my computer?

rtmistler · 07-20-2017, 06:52 AM

First read is that there appears to be a very lengthy filename starting with a dot.

But did you hit TAB after you did the "cat ."? You imply that you hit the 'b' and this happened.

Have you investigated with an "ls -al" command to view this file or phenomena? Suggest you do this, and suggest you enlarge that terminal window to see more all at once if you can. Find out what that is.

Or, are you saying that you just hit the 'b' and suddenly it streamed that, and then this is why you had to hit the CTRL-C?

How about things like a reboot, a shutdown and restart, or a closing of that terminal window and a new one?

I have encountered messed up I/O on a terminal window from something like cat'ing a binary file. And have had to close the terminal to create a new one. Rarely have I had to reboot or shutdown, but there have been times where things have been messed up enough that I've had to take that action. Have you tried any of those actions?

malekmustaq · 07-20-2017, 07:12 AM

Hi,

Usually it is in how you set the environment. Check the language default

Code:

env | grep -i lang

if it is not in some english literate language there is likely a problem to issue. Try change it to LANG=en_US.UTF-8 and see if the problem goes.

Another possible solution is to go to the configuration menu and set your KEYBOARD to a common layout like 101-Keys-International or the like.

I certain came across that problem and I solved it easily from stipulating proper "locale" values and Keyboard Layout.

Hope this helps. Good luck.

m.m.

MadeInGermany · 07-20-2017, 01:47 PM

Can you start xterm in your terminal tool?
How is the behavior in the xterm?

suicidaleggroll · 07-20-2017, 02:11 PM

Quote:

Originally Posted by rtmistler

I have encountered messed up I/O on a terminal window from something like cat'ing a binary file. And have had to close the terminal to create a new one. Rarely have I had to reboot or shutdown, but there have been times where things have been messed up enough that I've had to take that action. Have you tried any of those actions?

FYI - "reset" typically fixes this condition. Even if you can't see the letters as you type reset, just do it, hit enter, and 99% of the time it'll clear everything up and go back to normal.