[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: buffer name completion is case-sensitive now

From: John Paul Wallington
Subject: Re: buffer name completion is case-sensitive now
Date: Sun, 8 Jun 2008 18:29:22 +0100

On 8 Jun 2008, at 17:40, Drew Adams wrote:

Sometime between April 19 and May 4, at least on Windows, buffer- name completion
seems to have been changed to become case-sensitive.

I have been annoyed by this, and I just got a message from an Icicles user who complained of the same thing, thinking it had something to do with Icicles.

Was this change intentional? I didn't notice any discussion of it here, and I can find nothing in NEWS about it? I'm surprised no one has mentioned this yet.

The change is experimental rather than final. I've documented it in NEWS for now.

To me, this is a bug. If this is intentional, however, count me as one vote against it. If the decision is final, then how about at least adding a user option to deal with this? Users should not need to redefine `read- buffer' or commands that use buffer-name completion, just to bind `completion- ignore-case'
to non-nil.

With the introduction of `read-file-name-completion-ignore-case' there's less need to have an MS-Windows specific default value of `completion-ignore-case'. However, buffer names -- particularly those that are based upon filenames -- would probably benefit from case-insensitivity in completion, at least on systems with case insensitive file systems. Are there any other examples where case sensitivity is problematic?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]