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. DrewReceived on Fri May 06 2005 - 11:06:54 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:34 UTC