From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Oleh Krehel <ohwoeowho@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Questions about the `completing-read-function' interface
Date: Fri, 17 Apr 2015 11:31:48 -0400 [thread overview]
Message-ID: <jwvy4lqvkvt.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87oammn75z.fsf@gmail.com> (Oleh Krehel's message of "Fri, 17 Apr 2015 16:47:20 +0200")
>> So far we haven't tried to enforce this and if require-match is not set,
>> then I don't think we should require it.
> I agree for the case of
> (memq require-match '(nil confirm confirm-after-completion))
> What about the other cases?
If require is t I think it'd be OK for the completing-read function to
ignore any DEF argument which is not in COLLECTION.
For the same reason, M-p should arguably skip history members which
aren't in COLLECTION (or which are rejected by PRED).
But there are some issues: even if DEF (or history elements) would be
rejected by require-match when you hit RET, it might still be a useful
string to get via M-n (which the user then completes before hitting RET).
> 1. all minor modes subscribe with `set-completing-read-function'
> 2. user calls M-x mode-1. mode-1 is active and subscribes.
> 3. user calls M-x mode-2. Emacs sends a message to mode-1 to shut
> down. mode-2 is active and subscribes.
> 4. and so on.
But this extra complexity only "solves" the very narrow problem you're
facing, while introducing non-trivial issues: what about minor modes
that override completing-read-function but which only apply to some
cases? There can be several such minor modes active at the same time
without conflict.
> There's no way to end up in a worse state than is now.
Well yes, there is: increase code complexity for little benefit is
a worse state.
>> I agree that there are potential for actual problems if the
>> completing-read-function is not properly reverted when the modes are
>> disabled. For that reason I recommend you use `add-function' and
>> `remove-function' rather than `setq'.
> I don't understand. Can you give an example?
M-x ivy-mode RET
M-x helm-mode RET
M-x ivy-mode RET
You should now have helm-mode active and working properly, yet with your
current code, helm-mode will be "enabled by inactive". If you use
add/remove-function this case will be handled correctly.
Stefan
next prev parent reply other threads:[~2015-04-17 15:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 9:59 Questions about the `completing-read-function' interface Oleh Krehel
2015-04-17 14:10 ` Drew Adams
2015-04-17 14:32 ` Oleh Krehel
2015-04-17 15:06 ` Drew Adams
2015-04-17 14:18 ` Stefan Monnier
2015-04-17 14:47 ` Oleh Krehel
2015-04-17 15:31 ` Stefan Monnier [this message]
2015-04-17 15:40 ` Oleh Krehel
2015-04-17 18:04 ` Stefan Monnier
2015-04-17 18:15 ` Oleh Krehel
2015-04-17 19:05 ` Stefan Monnier
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=jwvy4lqvkvt.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=ohwoeowho@gmail.com \
/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.