Still having problems with \n in PS1 (& other readline comments)

Article View: gnu.bash.bug

Article #741

#741

From: Brian Fox
Date: Fri, 17 Nov 1989 02:50

18 lines
1137 bytes

   Posted-Date: Thu, 16 Nov 89 13:50:49 -0500
   Date: Thu, 16 Nov 89 13:50:49 -0500
   From: Chet Ramey <chet@cwns1.INS.CWRU.Edu>
   Reply-To: chet@po.CWRU.Edu

   <tale@pawl.rpi.edu> says:
   > 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 don't think this is a good idea.  Possible completions should never be
   shown unless asked for explicitly.

I think it deserves a vote.  If enough people want it, I will make it a
variable in .inputrc.

Brian

Technical Details

Message-ID: <8911170250.AA09050@aurel.cns.caltech.edu.>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!watmath!uunet!tut.cis.ohio-state.edu!AUREL.CNS.CALTECH.EDU!bfox

References: <8911161850.AA05051@cwns1.INS.CWRU.Edu>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!watmath!uunet!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: <8911170250.AA09050@aurel.cns.caltech.edu.>
Date: 17 Nov 89 02:50:06 GMT
References: <8911161850.AA05051@cwns1.INS.CWRU.Edu>
Sender: daemon@tut.cis.ohio-state.edu
Reply-To: bfox@aurel.cns.caltech.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 18

Reply to Parent Message