On 3/16/17 1:49 PM, Roee Bar wrote:
> 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
On 3/15/17 1:56 PM, Roee Bar wrote:
> Thanks Chet.
>
> I found out it happens only when I have this one is in my .inputrc:
> set completion-ignore-case on
OK, that helped me find it. It will be fixed in the next devel branch
push. Thanks.
Chet
--
``The lyf so short, the craft so long to lerne
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
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
consi
