all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 56508@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>
Subject: bug#56508: Suggestions for the "Help" menu
Date: Tue, 12 Jul 2022 21:35:18 +0800	[thread overview]
Message-ID: <87czeawj1l.fsf@yahoo.com> (raw)
In-Reply-To: <83wncjxdcx.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 12 Jul 2022 05:40:30 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> I believe we should leave that menu alone.

I agree.  In fact, the current arrangement of the Help and Options menus
is also very useful for finding bugs in GUI code.  The development of
the Haiku port would not have been possible without the deeply nested
internationalization menus.





      parent reply	other threads:[~2022-07-12 13:35 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
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 [this message]

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=87czeawj1l.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=56508@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    --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 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.