From: Thierry Volpiatto <thievol@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, 64902@debbugs.gnu.org
Subject: bug#64902: 30.0.50; REQUIRE-MATCH completing-read arg in describe-* commands
Date: Fri, 28 Jul 2023 05:41:00 +0000 [thread overview]
Message-ID: <87jzukmvub.fsf@posteo.net> (raw)
In-Reply-To: <jwvbkfwg29w.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> `completing-read` REQUIRE-MATCH arg in describe-variable == t,
>>> describe-symbol == t and describe-function == 'confirm ?
>>>
>>> I see no reasons why `describe-function` uses 'confirm but maybe I am
>>> missing something?
>>
>> Stefan (CC'ed) made that change last September, and it looks
>> deliberate.
>>
>> Stefan?
>
> I'm not sure what was the situation that motivated it, because I failed
> to write it in the comment or commit message :-(
> I suspect it might have been when a function is advised but not yet defined.
Hmm, how could this happen? The problem is that with Helm completion I
have an extra unknow symbol on top of list when I start typing (this is
expected when require-match is non-nil), not very
annoying but I am pretty sure I will have bug reports about this.
>
> Stefan
--
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 686 bytes --]
next prev parent reply other threads:[~2023-07-28 5:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 14:52 bug#64902: 30.0.50; REQUIRE-MATCH completing-read arg in describe-* commands Thierry Volpiatto
2023-07-27 16:57 ` Eli Zaretskii
2023-07-28 3:12 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-28 5:41 ` Thierry Volpiatto [this message]
2023-07-28 14:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-28 16:16 ` Thierry Volpiatto
2023-07-29 5:28 ` Thierry Volpiatto
2023-08-03 8:28 ` Eli Zaretskii
2023-08-03 13:30 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-03 21:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-05 6:51 ` Thierry Volpiatto
2023-08-15 14:23 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-15 15:41 ` Thierry Volpiatto
2023-08-15 16:34 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-15 17:00 ` Thierry Volpiatto
2023-08-05 6:39 ` Thierry Volpiatto
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=87jzukmvub.fsf@posteo.net \
--to=thievol@posteo.net \
--cc=64902@debbugs.gnu.org \
--cc=eliz@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).