From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 56508@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>, miha@kamnitnik.top
Subject: bug#56508: Suggestions for the "Help" menu
Date: Tue, 12 Jul 2022 21:31:38 +0800 [thread overview]
Message-ID: <87k08iwj7p.fsf@yahoo.com> (raw)
In-Reply-To: <CADwFkmkru48RHOcaxnCuVeM2hi0z56-QOAh=1_QXqZgUiRhTDQ@mail.gmail.com> (Stefan Kangas's message of "Tue, 12 Jul 2022 05:10:06 -0500")
Stefan Kangas <stefan@marxist.se> writes:
>> Perhaps we could replace it with "Describe Coding System", that is, the
>> describe-current-coding-system command, which shows an easier to
>> understand *Help* buffer.
>
> That would be much more usable for a non-expert like me, indeed.
Why would we replace that with the item that is displayed above it?
next prev parent reply other threads:[~2022-07-12 13:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 2:04 bug#56508: Suggestions for the "Help" menu Stefan Kangas
2022-07-12 2:40 ` Eli Zaretskii
2022-07-12 3:16 ` Stefan Kangas
2022-07-12 8:26 ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-12 10:10 ` Stefan Kangas
2022-07-12 13:14 ` Lars Ingebrigtsen
2022-07-12 13:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-07-12 13:15 ` Eli Zaretskii
2022-07-12 12:54 ` Eli Zaretskii
2022-07-12 13:37 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-12 13:54 ` Stefan Kangas
2022-07-12 14:04 ` Stefan Kangas
2022-07-12 14:21 ` Eli Zaretskii
2022-07-12 15:25 ` Drew Adams
2022-07-12 15:20 ` Drew Adams
2022-07-12 13:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87k08iwj7p.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=56508@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=miha@kamnitnik.top \
--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).