all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 14942@debbugs.gnu.org
Subject: bug#14942: 24.3.50; Improve key descriptions for facemenu menu items
Date: Tue, 23 Jul 2013 22:30:07 -0700 (PDT)	[thread overview]
Message-ID: <20a01510-8eb7-4920-a7b9-0dcecdd73845@default> (raw)

`C-h f facemenu-set-invisible' says that the command is bound to
<C-down-mouse-2> <sp> v, <menu-bar> <edit> <props> <sp> v.

Good luck trying to understand that, Ms User.  And yet it is so close.

This would be a lot more helpful for users if we simply used reasonable
names for the menu-item pseudo-function keys.  Instead of <sp> use
<special-properties> and things suddenly become much clearer.  Likewise,
use <text-properties> instead of <props>.  Likewise, use <invisible>
instead of just [?v].

There is no reason to take shortcuts coding this kind of thing.  Keep
in mind that the names used for menu-item keys are part of the user
interface.  Please make an effort to provide names that help users
instead of just looking for a quick abbreviation.

In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
 of 2013-07-14 on ODIEONE
Bzr revision: 113423 lekktu@gmail.com-20130715004922-i67tg2ois14h3fpm
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/Devel/emacs/binary --enable-checking=yes,glyphs
 CFLAGS='-O0 -g3' CPPFLAGS='-Ic:/Devel/emacs/include'
 LDFLAGS='-Lc:/Devel/emacs/lib''





             reply	other threads:[~2013-07-24  5:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24  5:30 Drew Adams [this message]
2016-04-29 13:18 ` bug#14942: 24.3.50; Improve key descriptions for facemenu menu items Lars Ingebrigtsen
2016-04-29 13:35   ` Eli Zaretskii
2016-04-29 13:39     ` Lars Ingebrigtsen
2016-04-29 13:57       ` Eli Zaretskii
2016-04-29 14:10         ` Lars Ingebrigtsen
2016-04-29 16:10           ` Andreas Schwab

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=20a01510-8eb7-4920-a7b9-0dcecdd73845@default \
    --to=drew.adams@oracle.com \
    --cc=14942@debbugs.gnu.org \
    /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.