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).
> On Mar 15, 2017, at 10:56, Roee Bar <r...@arista.com> wrote: > > Thanks Chet. > > I found out it happens only when I have this one is in my .inputrc: > set completion-ignore-case on > > Regards, > Roee > >> On Mar 15, 2017, at 04:50, Chet Ramey <chet.ra...@case.edu> wrote: >> >> On 3/15/17 1:54 AM, r...@arista.com wrote: >> >>> Bash Version: 4.3 >>> Patch Level: 42 >>> Release Status: release >>> >>> Description: >>> dabbrev-expand supposed to menu complete using history where most >>> recent entries are presented first. However, it seems like the entries are >>> sorted. >>> This is from the release notes of bash-4.1: "Changes to dabbrev-expand >>> to make it more `emacs-like': no space appended after matches, completions >>> are not sorted, and most recent history entries are presented first. >>> This bug has been verified on bash 4.4 as well as on bash 4.3. >> >> I can't reproduce this on bash-4.4. If I bind dabbrev-expand to, say, >> "\C-x\C-d" and follow the steps in your report, I cycle through ~/tmp3, >> ~/tmp2, and ~/tmp1 as possible completions when I hit C-xC-d. >> >> You might check whether or not you have a programmable completion for `ls' >> that could be sorting the matches. >> >> Chet >> -- >> ``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/ >
