Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!HUB.UCSB.EDU!bfox%vision
From: bfox%vision@HUB.UCSB.EDU (Brian Fox)
Newsgroups: gnu.bash.bug
Subject: Question about vi-mode
Message-ID: <8911110005.AA09154@hub.ucsb.edu>
Date: 11 Nov 89 00:05:08 GMT
References: <1989Nov9.023842.28689@rpi.edu>
Sender: daemon@tut.cis.ohio-state.edu
Reply-To: bfox%cornu@hub.ucsb.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 22


   Posted-Date: 9 Nov 89 02:38:42 GMT
   Date: 9 Nov 89 02:38:42 GMT
   From: rpi!night@cis.ohio-state.edu  (Trip Martin)
   Organization: Rensselaer Polytechnic Institute, Troy NY
   Sender: bug-bash-request@prep.ai.mit.edu

   I just got bash up and running on a 3B2, and looking through the
   documentation, I noticed that the only way to enter vi-mode is by
   having a .inputrc when the program is first run.  There are times when
   I would like to be able to switch to vi-mode after bash is already
   running.  Why is the extra rc file (.inputrc) necessary, and why is
   that the only way to enter vi-mode?  

M-C-j toggles between the two modes.

Placing "set editing-mode vi" in your .inputrc file brings up line editing
in vi mode.

Typing C-x C-r re-reads your .inputrc file.

Brian