There is no ambiguous in dabbrev-expand - it is well defined what the completion should be: each key press cycles through the matches from most recent to oldest match. This is different than TAB completion, where it is possible to have several matches so it makes sense to display them. That is also the dabbrev-expand behaviour in tcsh when ‘autolist’ (i.e. 'show-all-if-ambiguous’ ) is set.
Also, have you succeeded reproducing the original dabbrev-expand bug with completion-ignore-case set? > On Mar 16, 2017, at 08:56, Chet Ramey <chet.ra...@case.edu> wrote: > > On 3/15/17 4:25 PM, Roee Bar wrote: >> Also, not as serious as the bug below, if you have 'set >> show-all-if-ambiguous on’ on your .inputrc, it shows all matching on >> dabbrev-expand as well (I don’t think it should). > > I think it should. If you have that variable enabled, you want it to act > consistently for all completions. > > -- > ``The lyf so short, the craft so long to lerne.'' - Chaucer > ``Ars longa, vita brevis'' - Hippocrates > Chet Ramey, UTech, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
