Date: Fri, 6 May 2005 09:08:08 +0100 From: Brian Candler <B.Candler@pobox.com> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: freebsd-current@freebsd.org Subject: Re: boot banner project Message-ID: <20050506080808.GA967@uk.tiscali.com> In-Reply-To: <17018.7931.658513.492252@grasshopper.cs.duke.edu> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
Regards,
Brian.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050506080808.GA967>