[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#65089: 30.0.50; shell-command filename completion unexpected behavio
From: |
Mauro Aranda |
Subject: |
bug#65089: 30.0.50; shell-command filename completion unexpected behavior change |
Date: |
Sat, 2 Sep 2023 19:01:12 -0300 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 |
On 2/9/23 17:07, Stefan Kangas wrote:
> Mauro Aranda <maurooaranda@gmail.com> writes:
>
>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>
>> >>> Now, with emacs -Q:
>> >>> M-!
>> >>> ls ~/bug/bar
>> >>> Put point between "/" and "b" of "bar" and type TAB
>> >>> emacs says "No match", but I expected it to offer completions,
>> foo-1 and
>> >>> foo-2.
>> >>>
>> >>> That was the behavior, at least in Emacs 28. Reverting the
following
>> >>> commit, returns this behavior for me:
>> >
>> > The patch below adds yet another heuristic to try and handle the
>> > current case, but really we should rework the pcomplete API so as to
>> > provide us the right info to start with.
>>
>> I see. Thanks for your explanation. In the meantime, I confirm that
>> your patch fixes this use case.
>
> Was this installed? I only see that the bug was left open.
It looks like it wasn't installed.