This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: can't type 's'
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Dai Itasaka <ditasaka at silverbacksystems dot com>
- Cc: cygwin at cygwin dot com
- Date: Wed, 7 Apr 2004 20:53:36 -0400 (EDT)
- Subject: Re: can't type 's'
- References: <007a01c41d01$bf2da930$7b05000a@corp.silverbacksystems.com>
- Reply-to: cygwin at cygwin dot com
On Wed, 7 Apr 2004, Dai Itasaka wrote:
> Hello all,
>
> I can't type 's'. If I escape it with Ctrl-V, then I can see it.
> If I type the word "mississippi", I get "miiippi". Some folks
> remember the thread on the Cygwin/X ML? That was last October.
> I thought it was related to the X because I got this on xterm,
> but it turned out to be a non-X issue because it happens on
> the console windows too.
>
> This happens on the bash prompt. Since I prefer tcsh to bash
> and I don't have this problem on the tcsh prompt, this wasn't
> such a big issue to me.
>
> Now, the same thing happens on the prompt of the gdb command
> invoked from tcsh. It matters to me now.
>
> What is the fix? Is it true that it is related to ~/.inputrc?
> I appreciate your help.
> Thanks,
> Dai
That's very easy to check -- just rename ~/.inputrc temporarily and see if
it fixes the problem.
It does sound like a readline configuration problem. What's the output of
bind -p | grep '^"s"'
on your system? What do you have in your ~/.inputrc? An alternative way
to provide readline configuration is by putting "bind" commands in
~/.bashrc or ~/.bash_profile, so check those as well.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
--
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/