all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>
Cc: emacs-devel@gnu.org
Subject: RE: menu-bar-help-menu
Date: Fri, 16 Nov 2018 09:04:55 -0800 (PST)	[thread overview]
Message-ID: <b745129c-08e3-48b2-a6c2-35f7dbfbfe63@default> (raw)
In-Reply-To: <<83d0r5795f.fsf@gnu.org>>

> > I often find help menu to be very useful.  I think the word "Emacs" is
> > too often shown up in the help menu.  Most of "Emacs" in the help menu
> > could be taken out to read better.  I propose the new help menu as
> > shown below.
> 
> FWIW, I think removing "Emacs" from these items will make their intent
> less clear.  I also don't understand how their presence can make the
> items less readable, can you explain?

Adding "Emacs" all over the place just adds noise, making
it harder to scan and pick out the signal.

Of course, if there is somewhere where a distinction
is important (Emacs vs something else), adding "Emacs"
might help in that case.  But adding it gratuitously
in many places prevents such an exception from standing
out.



       reply	other threads:[~2018-11-16 17:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<20181116.132016.345008228744400751.tkk@misasa.okayama-u.ac.jp>
     [not found] ` <<83d0r5795f.fsf@gnu.org>
2018-11-16 17:04   ` Drew Adams [this message]
2018-11-20  3:34     ` menu-bar-help-menu Van L
2018-11-16  4:20 menu-bar-help-menu Tak Kunihiro
2018-11-16  7:51 ` menu-bar-help-menu Eli Zaretskii
2018-11-17  0:02   ` menu-bar-help-menu Tak Kunihiro
2018-11-17  7:17     ` menu-bar-help-menu Eli Zaretskii
2018-11-18  1:31       ` menu-bar-help-menu Tak Kunihiro
2018-11-16 17:01 ` menu-bar-help-menu Drew Adams

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=b745129c-08e3-48b2-a6c2-35f7dbfbfe63@default \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=tkk@misasa.okayama-u.ac.jp \
    /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.