From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: rudalics@gmx.at, 60252@debbugs.gnu.org
Subject: bug#60252: 29.0.60; help-fns--describe-function-or-command-prompt asks for confirmation
Date: Fri, 23 Dec 2022 09:26:41 +0200 [thread overview]
Message-ID: <83cz8a8tse.fsf@gnu.org> (raw)
In-Reply-To: <jwvlemz2lj4.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 22 Dec 2022 16:14:04 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: rudalics@gmx.at, 60252@debbugs.gnu.org
> Date: Thu, 22 Dec 2022 16:14:04 -0500
>
> >> We may as well revert that part of my patch.
> > I don't think that would be TRT. Emacs behaves like that in other
> > places, so why this one should be different? Such inconsistency can
> > confusing.
>
> It's quite unusual to ask for the `describe-function` of a symbol that's
> not defined as a function and it won't give you very much info.
I'm afraid of use cases where the user didn't know whether a function
is or isn't defined. Human memory isn't perfect. I frequently forget
whether the function is buffer-process or get-buffer-process, for
example.
next prev parent reply other threads:[~2022-12-23 7:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 9:21 bug#60252: 29.0.60; help-fns--describe-function-or-command-prompt asks for confirmation martin rudalics
2022-12-22 10:54 ` Eli Zaretskii
2022-12-22 14:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-22 15:30 ` Eli Zaretskii
2022-12-22 16:41 ` martin rudalics
2022-12-22 16:48 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-22 16:53 ` Eli Zaretskii
2022-12-22 21:14 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-23 7:26 ` Eli Zaretskii [this message]
2022-12-22 21:32 ` Gregory Heytings
2022-12-22 23:25 ` Drew Adams
2022-12-23 7:02 ` Juri Linkov
2022-12-23 14:43 ` Eli Zaretskii
2022-12-23 16:36 ` Drew Adams
2022-12-23 7:32 ` Eli Zaretskii
2022-12-23 16:47 ` Drew Adams
2022-12-23 18:43 ` Eli Zaretskii
2022-12-23 20:45 ` Drew Adams
2022-12-24 6:43 ` Eli Zaretskii
2022-12-23 7:24 ` Eli Zaretskii
2022-12-23 11:21 ` Gregory Heytings
2022-12-23 12:39 ` Eli Zaretskii
2022-12-23 8:33 ` martin rudalics
2022-12-23 11:19 ` Gregory Heytings
2022-12-24 8:38 ` martin rudalics
2022-12-23 11:34 ` Eli Zaretskii
2022-12-24 8:38 ` martin rudalics
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=83cz8a8tse.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60252@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rudalics@gmx.at \
/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).