From: Eli Zaretskii <eliz@gnu.org>
To: Thierry Volpiatto <thievol@posteo.net>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 64902@debbugs.gnu.org
Subject: bug#64902: 30.0.50; REQUIRE-MATCH completing-read arg in describe-* commands
Date: Thu, 27 Jul 2023 19:57:56 +0300 [thread overview]
Message-ID: <83ila5l2az.fsf@gnu.org> (raw)
In-Reply-To: <874jlp8kt2.fsf@posteo.net> (message from Thierry Volpiatto on Thu, 27 Jul 2023 14:52:14 +0000)
> From: Thierry Volpiatto <thievol@posteo.net>
> Date: Thu, 27 Jul 2023 14:52:14 +0000
>
>
> `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?
next prev parent reply other threads:[~2023-07-27 16:57 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ila5l2az.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64902@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=thievol@posteo.net \
/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.