Path: utzoo!mnetor!tmsoft!torsqnt!jarvis.csri.toronto.edu!rutgers!ucsd!tut.cis.ohio-state.edu!AUREL.CNS.CALTECH.EDU!bfox
From: bfox@AUREL.CNS.CALTECH.EDU (Brian Fox)
Newsgroups: gnu.bash.bug
Subject: Still having problems with \n in PS1 (& other readline comments)
Message-ID: <8911180103.AA11388@aurel.cns.caltech.edu.>
Date: 18 Nov 89 01:03:18 GMT
References: <PERF.89Nov18003645@osiris.efd.lth.se>
Sender: daemon@tut.cis.ohio-state.edu
Reply-To: luth!sunic!urd!newsuser@bfox@aurel.cns.caltech.edu.date.17.nov.89.23.37.21.gmt.from.eru       
        
      (Per Foreby),
        Lund.Institute.of.Technology@aurel.cns.caltech.edu,
        Lund@aurel.cns.caltech.edu,
        Sweden
   References: <1989
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 29


   In article <1989Nov16.065930.23255@rpi.edu> tale@pawl.rpi.edu (David C Lawrence) writes:

   > 
   > Brian, you say that you don't like the way C-d is context dependent in
   > tcsh (which, by the way, is not local to Rutgers; it is standard
   > tcsh).  How about making TAB work like Emacs does in completing reads?
   > If TAB can't add any non-ambiguous characters from point then it shows
   > completions otherwise it adds in what can.
   > 
   I found that C-x isn't bound to anything per default. C-x is almost as
   easy to type as C-d so I added it to my $HOME/.inputrc:

	   C-x:    possible-completions

   Maybe this binding should be default?

   --
   Per Foreby
   System manager at EFD, Lund Institute of Technology (Lund University)
   Snail: E-huset, Tekniska Hogskolan i Lund, Box 118, S-221 00 LUND, Sweden. 
   Email: perf@efd.lth.se		Phone: int + 46 46-10 74 92

Whoops.  In 1.04 C-x is a prefix character for several commands.
One of them is C-x C-r (re-read-init-file).

There are also keyboard macro commands, like C-x ( and C-x ).

Brian