Mail Archives: cygwin/2004/09/08/08:50:40
On Wed, 8 Sep 2004, Rado Rethmann wrote:
> Ok, now I've discovered, that it must be something in my .inputrc file:
> --------------------------------------------
> [45-line .inputrc] snipped
> --------------------------------------------
> Which line tells Cygwin to wipe out my 'e' ? Rado
Why not try a binary search (comment out half, see if your <e> is back,
repeat until you find the culprit), or even a linear search (with only 45
lines it shouldn't take that long)?
FWIW, accidentally omitting a "\" somewhere in the "\e" binding would
result in the symptoms you described. Particularly, key binding may be
done not only in the .inputrc, but also in any of the startup scripts (via
the "bind" bash builtin). Check those carefully, because you'll need to
single quote the double quotes for those bindings (with just double
quotes, "\e" may be interpreted as a literal "e").
HTH,
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Happiness lies in being privileged to work hard for long hours in doing
whatever you think is worth doing." -- Dr. Jubal Harshaw
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -