unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stefan Kangas <stefan@marxist.se>, Eli Zaretskii <eliz@gnu.org>
Cc: "56508@debbugs.gnu.org" <56508@debbugs.gnu.org>
Subject: bug#56508: Suggestions for the "Help" menu
Date: Tue, 12 Jul 2022 15:25:43 +0000	[thread overview]
Message-ID: <SJ0PR10MB548892FA9E2FB4DAD6B50FD3F3869@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <CADwFkmnNDh=pE=XiPYFJwjyV6HfnGOrXMJ4iXXSHyVnEuzGtSQ@mail.gmail.com>

> overall the "Help" menu does feel overwhelming.

Some people find a table of contents or an index
overwhelming.  Others find them useful.

> Anything we could remove from it would help,

Why do you think so?

We could remove _everything_ from it.  Scrubbed
clean - spick & span.  Why would that help?

  parent reply	other threads:[~2022-07-12 15:25 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
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 [this message]
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=SJ0PR10MB548892FA9E2FB4DAD6B50FD3F3869@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=56508@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).