On Tue, 23 Oct 2001, John Gaughan wrote:
> Not quite all, since your supplying a command to run (i.e., it's not an
> interactive shell) the GNU readline library isn't used (readline
> provides the command-line interface in bash, it's also used by other
> programs such as ncftp and gdb). The readline startup files appear to
> be read after bash's startup files, so they could be overriding the "set
> -o emacs" in your bash startup files.
>> Readline is controlled by the files /etc/inputrc and ~/.inputrc. The
> default key bindings are controlled by the "editing-mode" variable
> (there's also a "keymap" variable, but as far as I can tell this
> doesn't do anything). To set the key bindings to vi you'd add the line
> "set editing-mode vi" to your .inputrc (or "set editing-mode emacs" for
> emacs key bindings). You can see what your readline variables are set
> to with "bind -V".
Brilliant John, it was indeed the .inputrc. Both keymap and editing-mode
were set to vi so they're both changed back to emacs and all is well with
my shell again,
Thanks
Gavin
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
