bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: old-menu-complete behavior in bash v4 / readline v6


From: Chet Ramey
Subject: Re: old-menu-complete behavior in bash v4 / readline v6
Date: Tue, 15 Mar 2011 11:24:36 -0400
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.14) Gecko/20110221 Thunderbird/3.1.8

On 3/15/11 11:13 AM, Alan wrote:
> Thanks for the response!
> 
> The problem is, if I turn off 'show-all-if-ambiguous', hitting tab
> won't display all the possible completions. I like the old behavior of
> 'menu-complete' because if I wanted to display the completions, I
> could always hit tab before purely cycling through the choices with
> 'menu-complete.' So it gives more flexibility in my opinion.
> 
> Plus, I expected something with the name, 'old-menu-complete,' to
> behave like the old 'menu-complete' did, but I digress...

Sure, modulo any bug fixes.  It was, as I said, a bug that the menu
completion function didn't behave like other completion functions and
honor the setting of show-all-if-ambiguous.  That was changed in the
readline-6.2 development cycle before I changed the behavior more
radically and split the old from the new.

> What would be the best way for me to make old-menu-complete behave
> like menu-complete did pre-readline-6.0? (In other words, behave like
> 'show-all-if-ambiguous' is off, while it is really on for other stuff
> like tab.) Would it be best to write some sort of bash function? Or
> would it be better to just modify the source code?

You'll have to modify the source code.

Chet
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]