From: David Kastrup <dak@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jpw@pobox.com, emacs-devel@gnu.org, monnier@iro.umontreal.ca,
Miles Bader <miles@gnu.org>
Subject: Re: add `read-buffer-completion-ignore-case' ?
Date: Mon, 09 Jun 2008 11:09:44 +0200 [thread overview]
Message-ID: <86zlpv6kkn.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <u63sjknd9.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 09 Jun 2008 11:45:38 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Miles Bader <miles.bader@necel.com>
>> Date: Mon, 09 Jun 2008 11:59:21 +0900
>> Cc: emacs-devel@gnu.org, John Paul Wallington <jpw@pobox.com>
>>
>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> > I don't think we need yet-another configuration variable for that.
>> > We should just reuse read-file-name-completion-ignore-case.
>>
>> Regardless of what some newbies think, buffer names and filenames are
>> not the same. It is quite reasonable for someone to want to have one be
>> case-insensitive but not the other.
>
> I don't necessarily disagree, but we do know which buffers are
> associated with a file and which aren't. So we could DWIM in each
> case as appropriate. If we want that, of course.
I don't think we do. For non-file buffers, I don't really see that
having different completion realms for "*Messages*" and "*mail*" is
really an essential part of people's workflow. So it is not that
important to differentiate here as well.
What about buffers associated with a file, but with a file name not
matching the buffer name?
There is so much potential for messiness that I would not want to go
there.
--
David Kastrup
next prev parent reply other threads:[~2008-06-09 9:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-08 21:28 add `read-buffer-completion-ignore-case' ? John Paul Wallington
2008-06-08 22:46 ` Drew Adams
2008-06-08 22:51 ` doc strings for read-*-completion-ignore-case [was: add `read-buffer-completion-ignore-case' ?] Drew Adams
2008-06-09 1:53 ` add `read-buffer-completion-ignore-case' ? Stefan Monnier
2008-06-09 2:59 ` Miles Bader
2008-06-09 6:45 ` Drew Adams
2008-06-09 8:45 ` Eli Zaretskii
2008-06-09 9:09 ` David Kastrup [this message]
2008-06-09 9:10 ` Juanma Barranquero
2008-06-10 1:15 ` Stefan Monnier
2008-06-10 1:26 ` Miles Bader
2008-06-10 2:41 ` Stefan Monnier
2008-06-09 12:10 ` John Paul Wallington
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86zlpv6kkn.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jpw@pobox.com \
--cc=miles@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).