This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Subject: Re: set options in bash From: Olmy <olmy@thistledown.org> Date: Thu, 17 Feb 2000 10:28:15 -0600 (CST) On Thu, 17 Feb 2000, Olmy wrote: > > I'm having a rather curious problem and wondered if anyone had some input: > > I can set -o vi at the bash prompt and will get correct functioning > of the shell, shell editor environment, and history viewing/editing (as > per the vi-like shell editing option). > > Further, I can add set -o vi to my .bashrc and manually source the > config file (. .bashrc) and will also get correct shell behaviour. > > However, if I leave that set -o vi in the rc file, log out and log > back in, I lose my history viewing/editing capability. > > A diff of the output from set, set -o, and env under each shell > configuration doesn't turn up any obvious culprits. Last, $HISTCMD, > $HISTFILE, $HISTFILESIZE, $HISTSIZE all exist under both configurations -- > and problems there would have should up in comparative diffs of the env > output in each shell. > > I get the same behaviour with the rhcn bash-2 rpm. Ahh ... found something -- something of a bug in RH6.x that didn't exist in RH5.x or 4.x. If anyone's interested: http://linuxwww.db.erau.edu/mail_archives/redhat-devel-list/May_99/0112.html basically, the /etc/inputrc in RH6x contains some extra stuff that screws up set -o vi. The suggested fix was to use a $HOME/.inputrc with just: set input-meta on set convert-meta off set output-meta on and strip out the newer stuff. You'd use this instead of /etc/inputrc by setting a user-specific $INPUTRC value in your .bash_profile: INPUTRC=$HOME/.inputrc export INPUTRC ===