From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Kangas <stefan@marxist.se>
Cc: "52870@debbugs.gnu.org" <52870@debbugs.gnu.org>
Subject: bug#52870: [External] : bug#52870: Is displaying <menu-bar> bindings in describe-function useful?
Date: Thu, 30 Dec 2021 15:43:25 +0000 [thread overview]
Message-ID: <SJ0PR10MB54881E24E77D43849B51D69DF3459@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83tueqimwc.fsf@gnu.org>
+1 to all that Eli said.
___
It may come down to this: Some people might not
find this or that standard part of *Help* text
to be important, or even helpful. Other people
might find that same part to be helpful.
___
If the problem is that some people are annoyed
by seeing info they think isn't useful/helpful,
then a possible answer is to add the ability
for users to customize some of the parts, to
keep or remove them.
I suggested (and provided code for) the same
thing for `report-emacs-bug': letting a user
decide which automatically gathered info to
include.
Perhaps Stefan K would like to do something
similar for the standard parts of *Help*
output. IOW, instead of imposing a personal
preference on Emacs in general, give users a
way to customize the parts they do or don't
want to include. (And leave the default
behavior as is.)
next prev parent reply other threads:[~2021-12-30 15:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 12:40 bug#52870: Is displaying <menu-bar> bindings in describe-function useful? Stefan Kangas
2021-12-29 13:08 ` Lars Ingebrigtsen
2021-12-29 13:28 ` Eli Zaretskii
2021-12-29 14:49 ` Stefan Kangas
2021-12-29 16:51 ` Eli Zaretskii
2021-12-29 20:19 ` Stefan Kangas
2021-12-29 21:01 ` bug#52870: [External] : " Drew Adams
2021-12-30 7:15 ` Eli Zaretskii
2021-12-30 15:43 ` Drew Adams [this message]
2022-01-15 10:09 ` Lars Ingebrigtsen
2022-01-15 10:28 ` Eli Zaretskii
2022-01-20 11:02 ` Lars Ingebrigtsen
2022-01-15 10:29 ` Stefan Kangas
2022-01-15 12:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-15 22:50 ` bug#52870: [External] : " Drew Adams
2022-01-15 23:44 ` Stefan Kangas
2022-01-16 2:59 ` Drew Adams
2022-01-15 22:37 ` Drew Adams
2021-12-29 15:25 ` Drew Adams
2022-04-25 19:15 ` Lars Ingebrigtsen
2022-04-28 6:49 ` Juri Linkov
2022-04-28 10:17 ` Lars Ingebrigtsen
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=SJ0PR10MB54881E24E77D43849B51D69DF3459@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=52870@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stefan@marxist.se \
/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).