On 3/28/12 8:50 AM, Barry Downes wrote: > Short version: > I had a problem with bash/readline misinterpreting input sequences in vi > mode and erasing half my input line. To fix it I got my terminal to send > the less ambiguous "\eO[" instead of just "\e" for the escape key. But > there was a hack in the readline code which was still causing problems, so > I added the "vi-escape-hack" variable so I could disable the hack from my > .inputrc. The patch for this variable is attached. Naturally readline's > behaviour remains unchanged for the default value of the variable.
Take a look at the bug-bash thread containing http://lists.gnu.org/archive/html/bug-bash/2012-01/msg00094.html . That describes the addition of an inter-character timeout to readline for use in other contexts where it reads multi-character key sequences. I see no reason it won't work here also. If the timeout variable is set, it's used; if it's not, the current behavior is preserved. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRU [email protected] http://cnswww.cns.cwru.edu/~chet/ _______________________________________________ Bug-readline mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-readline
