1
I have Cygwin running on a Windows 7 Box. In what is a relatively new (and strange) development, the bash shell stopped recognizing the lowercase "t". For example:
I type
echo cat, output isca.
I typemore tmp.txt, output ismp.x does not exist(or however it says the file isn't there).
I typeecho TTT, output isTTT.
Anyone know about this one?
dgo
Posted 2013-06-26T19:22:42.747
Reputation: 685
It only doesn't recognise the lowercase "t"? Not uppercase? – Jon – 2013-06-26T19:33:27.967
1Sounds more like an issue with your terminal. Which one are you using (mintty, rxvt, cmd.exe, ...)? Do you see the same problem when you try a different one? – Costa – 2013-06-26T19:48:39.720
This should probably be closed as "too localized" but what a weird problem! Do you see the
tyou type or not? – terdon – 2013-06-26T20:24:26.257I doesn't happen with the command prompt (cmd.exe) which is what I primarily use. I currently have installed ConEmu, but the problem predates that. With Cygwin, bash is run in the existing command prompt shell, not in it's own shell. Putty ssh works fine, nodejs repl, cpan, mysql - any other software application that is run inside the existing shell. – dgo – 2013-06-26T20:30:45.410
I do see the 't' when I type it. It is just not outputted. – dgo – 2013-06-26T20:31:04.613
2Check your
~/.inputrcto see if you have anything special for readline. Also, checkbind -p– glenn jackman – 2013-06-26T20:46:23.060I'll be dammed. That was it. Using clink with ConEmu. This was the offending line:
"\t": clink-completion-shim. I assume that's for tab-completion. Do you know why that line caused the error? You should post your answer so I can vote for it. That was a hell of a catch. – dgo – 2013-06-26T21:21:22.2671My guess is that "" need so be double escaped like this "\t" – Nifle – 2013-06-26T21:25:53.800