[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-readline] re-read-init-file issue

From: Chet Ramey
Subject: Re: [Bug-readline] re-read-init-file issue
Date: Mon, 06 Apr 2009 17:47:57 -0400
User-agent: Thunderbird (Macintosh/20090302)

bob wrote:
> I have a "bind re-read-init-file" command in my .profile because I set
> INPUTRC with the file I want readline to use.

I'm not sure why.

That command attempts to bind the string "re-read-init-file", which
doesn't really mean anything.  The slightly arcane key name parsing
rules reduce that to `file' (since rl-read-init- isn't a valid
key sequence prefix, it gets thrown away), then to `f' (since the
old-style key binding syntax only allows you to bind a single key,
not a key sequence).  That gets bound to the null command, since
there's no command name following the key sequence.  When I do it,
I can't type `f' any more.

I assume you're using the history commands to re-run the grep.

> I am not sure why but when this command is run, even when there is not
> .inputrc file, it causes the "f" key to be remapped.
> Can you suggest a possible workaround?
> address@hidden:~$ bind -p|grep '"f"'
> "f": self-insert
> address@hidden:~$ echo $INPUTRC
> address@hidden:~$ ls -l ~/.inputrc
> ls: cannot access /home/bob/.inputrc: No such file or directory
> address@hidden:~$ bind re-read-init-file
> address@hidden:~$ bind -p|grep '"f"'
> "f": vi-char-search

When you use ESC-k to get back to the history entry you want to re-run,
the current keymap is set to the vi command keymap.  That's where `f'
is bound to vi-char-search.


``The lyf so short, the craft so long to lerne.'' - Chaucer

Chet Ramey, ITS, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]