Date: Fri, 6 May 2005 09:06:47 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Brian Candler <B.Candler@pobox.com> Cc: freebsd-current@freebsd.org Subject: Re: boot banner project Message-ID: <17019.27623.755948.347101@grasshopper.cs.duke.edu> In-Reply-To: <20050506080808.GA967@uk.tiscali.com> References: <B.Candler@pobox.com> <20050504150209.GA2516@uk.tiscali.com> <200505041646.j44GkKXw037042@fire.jhs.private> <20050504170737.GA15091@uk.tiscali.com> <17018.7931.658513.492252@grasshopper.cs.duke.edu> <20050506080808.GA967@uk.tiscali.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Brian Candler writes: > On Thu, May 05, 2005 at 09:26:19AM -0400, Andrew Gallatin wrote: > > In tcsh, hitting a tab once or 2 times results in the same thing -- > > filling in the path until there are multiple choices. So that > > second, accidental tab is harmless. > > > > But in bash, that second, accidental tab results in a long pause while > > the shell lists all the different choices for the completion of > > the path. Which I don't want to wait for. > > > > If I could make bash's completion act like tcsh completion (^D rather > > than tab-tab), I'd probably use it. > > >From bash(1): > > show-all-if-ambiguous (Off) > This alters the default behavior of the completion functions. > If set to on, words which have more than one possible completion > cause the matches to be listed immediately instead of ringing > the bell. > > Is that what you mean? No, that's even more confusing to me ;) What I want is to make completions work as much like tcsh as possble. Eg, any number of tabs completes up to the point where things diverge, and ctrl-D shows the possible options. Drew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17019.27623.755948.347101>