From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: completion-regexp-list and case-fold-search
Date: Sun, 4 Jan 2004 22:17:29 -0600 (CST) [thread overview]
Message-ID: <200401050417.i054HTW06220@raven.dms.auburn.edu> (raw)
In-Reply-To: <E1AdLc2-00051M-FE@fencepost.gnu.org> (message from Richard Stallman on Sun, 04 Jan 2004 22:41:06 -0500)
Richard Stallman wrote:
1. Make all the basic minibuffer completion functions bind
`case-fold-search' to the value of `completion-ignore-case' around
all calls to `{try,test}-completion' and `all-completions', as
`partial-completion-mode' already does.
That would be incorrect, since it would distort the behavior
of many user commands in the minibuffer.
Do we want to go for (1) or (2)? With (1) we are absolutely certain
that we do not break any code that was not already broken. (Because
all we do is make both values of `partial-completion-mode' consistent.)
Are you saying that partial-completion-mode does something analogous
to #1? If so, I think that is a bug, and we should replace that
with something analogous to #2.
I believe you misunderstood both proposal (1) and the behavior of
partial-completion-mode. They bind `case-fold-search' _only_
immediately around the calls to the basic completion functions.
During the recursive edit, the user customized value of
`case-fold-search' is in effect, in the minibuffer as elsewhere.
Nevertheless, I believe that proposal (2) is more intuitive, much
easier to document, and less prone to all kinds of bugs. So I will
implement proposal (2).
Sincerely,
Luc.
prev parent reply other threads:[~2004-01-05 4:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-01 3:17 completion-regexp-list and case-fold-search Luc Teirlinck
2004-01-05 3:41 ` Richard Stallman
2004-01-05 4:17 ` Luc Teirlinck [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200401050417.i054HTW06220@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.