GNU bug report logs -
#78323
Regression in case-insensitive filename completion
Previous Next
Full log
Message #36 received at 78323 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
It work for me as well, thank you.
Aaron
On Wed, May 14, 2025 at 4:37 AM, Dieter Deyke < dieter.deyke <at> gmail.com > wrote:
>
>
>
> Eli Zaretskii < eliz@ gnu. org ( eliz <at> gnu.org ) > writes:
>
>
>>
>>>
>>>
>>> From: Spencer Baugh < sbaugh@ janestreet. com ( sbaugh <at> janestreet.com ) >
>>> Cc: Stefan Monnier < monnier@ iro. umontreal. ca ( monnier <at> iro.umontreal.ca
>>> ) >, dancol@ dancol. org ( dancol <at> dancol.org ) , 78323@ debbugs. gnu. org (
>>> 78323 <at> debbugs.gnu.org )
>>> Date: Tue , 13 May 2025 12:23:36 -0400
>>>
>>>
>>>
>>> Eli Zaretskii < eliz@ gnu. org ( eliz <at> gnu.org ) > writes:
>>>
>>>
>>>>
>>>>>
>>>>>
>>>>> From: Stefan Monnier < monnier@ iro. umontreal. ca (
>>>>> monnier <at> iro.umontreal.ca ) > Cc: Daniel Colascione < dancol@ dancol. org (
>>>>> dancol <at> dancol.org ) >, sbaugh@ janestreet. com ( sbaugh <at> janestreet.com ) ,
>>>>> 78323@ debbugs. gnu. org ( 78323 <at> debbugs.gnu.org )
>>>>> Date: Mon , 12 May 2025 10:42:47 -0400
>>>>>
>>>>>
>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> With read-file-name-completion-ignore-case true, commit
>>>>>>>>> 509cbe1c35b3dd005a53ac041f9c87ee53b8e115 breaks existing completion
>>>>>>>>> behavior. Suppose we have file named fooBarQux. Previously, if I'd typed
>>>>>>>>> "foobar" and TAB while reading a filename, then the completion would be
>>>>>>>>> "fooBarQux". Now, it completes as "foobarQux", which is wrong and breaks,
>>>>>>>>> among other things, vc.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Spencer, could you please look into fixing this regression?
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> What do you think of reverting this change while Spencer finds the cause
>>>>>>> of the problem?
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> I wouldn't mind, but then I don't use these features. Let's hear Stefan's
>>>>>> opinion first.
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> I'd first like to hear Spencer's opinion on how quickly he might be able
>>>>> to fix it or if it indeed breaks his assumptions too hard (so we'd need a
>>>>> different approach, in which case we may as well revert the change first).
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> So, Spencer, the eyes of all the world are upon you.
>>>>
>>>>
>>>
>>>
>>>
>>> Sorry for the delay, I was away this weekend. Thanks for your patience.
>>>
>>>
>>>
>>> The attached patch should fix the issue; it's what I have installed at my
>>> site.
>>>
>>>
>>
>>
>>
>> Thanks.
>>
>>
>>
>> Daniel, Dieter, and Aaron, could you please see whether this fixes your
>> problems as well?
>>
>>
>
>
>
> Yes, it works for me now. Thanks!
>
>
>
> --
> Dieter Deyke
> mailto: dieter. deyke@ gmail. com ( dieter.deyke <at> gmail.com )
> Get my Gnupg key:
> gpg --keyserver keys. gnupg. net ( http://keys.gnupg.net/ ) --recv-keys
> B116EA20
>
>
>
[Message part 2 (text/html, inline)]
This bug report was last modified 27 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.