Path: utzoo!mnetor!tmsoft!torsqnt!jarvis.csri.toronto.edu!rutgers!shelby!bloom-beacon!eru!luth!sunic!Urd!newsuser From: perf@efd.lth.se (Per Foreby) Newsgroups: gnu.bash.bug Subject: Re: Still having problems with \n in PS1 (& other readline comments) Message-ID: Date: 17 Nov 89 23:37:21 GMT References: <1989Nov16.065930.23255@rpi.edu> Sender: newsuser@lth.se (LTH network news server) Organization: EFD, Lund Institute of Technology, Lund, Sweden Lines: 22 In-reply-to: tale@pawl.rpi.edu's message of 16 Nov 89 06:59:30 GMT 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