This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Bash 3.00.16(7), paste-from-clipboard binding reset after command execution
- From: zango <z_a_n_g_o at yahoo dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 5 Aug 2005 10:13:22 -0700 (PDT)
- Subject: Re: Bash 3.00.16(7), paste-from-clipboard binding reset after command execution
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>According to zango on 8/5/2005 6:37 AM:
>> I am seeing the same problem. I had a working
cygwin
>> installation. I downloaded a new package which
>> wouldn't work with the existing bash shell. So, I
>> updated the core libraries/bash and Control-V -
mapped
>> to "paste-from-clipboard" in my .inputrc stopped
>> working. "bind -p" now shows \C-v is mapped to
Quoted
>> Insert.
>> bind -f ~/.inputrc doesn't work either :(
>
>It has everything to do with your stty settings. ^v
is normally mapped to
>lnext (literal next-character) on terminals, and
readline 5.0 apparently
>tries to honor your stty settings (where lnext is a
perfect match to the
>readline function quoted-insert) in preference to
your .inputrc.
>Meanwhile, emacs likes ^q as quoted-insert, although
terminals usually
>default ^q to start, start overrides lnext if both
are given the same
>character, and stop (usually ^s) without start will
let you hang a
>terminal. So, try "stty lnext ^q stop undef start
undef" and see if that
>helps with your desired setting for ^v.
>
>As to whether readline should be prefering your stty
settings over your
>.inputrc, I will have to do more investigation.
>
>- --
>Life is short - so eat dessert first!
>
>Eric Blake ebb9@byu.net
>volunteer cygwin bash/readline maintainer
Thanks Eric,
Now, I've added
"stty lnext ^q stop undef start undef"
to my .bashrc and C-v works once again! :)
Regards,
girish
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
--
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/