From: M Jared Finder <jared@hpalace.com>
Subject: Re: substitute-command-keys to take optional `no-angles' arg?
Date: Sun, 17 Sep 2006 21:55:41 -0700 [thread overview]
Message-ID: <eel8sf$199$1@sea.gmane.org> (raw)
In-Reply-To: <MEEKKIABFKKDFJMPIOEBMEBEDFAA.drew.adams@oracle.com>
Drew Adams wrote:
> Function `substitute-command-keys' allows little control over a) which
> binding for a given command is used and b) the form of the key descriptions.
> We've discussed these a bit before, and agreed to re-discuss them after the
> release.
>
> For that discussion (after the release), it occurred to me that, wrt (b), it
> would be good to allow for a `no-angles' option for
> `substitute-command-keys', just as we do for `single-key-description'.
>
> For example, I use `substitute-command-keys' to provide a help string
> regarding some bindings, and it currently returns this:
>
> "(<S-tab>, TAB: list, C-h: help)"
>
> I would prefer to supply a `no-angles' argument to
> `substitute-command-keys', to get this, instead:
>
> "(S-tab, TAB: list, C-h: help)"
I'm just a user, so feel free to ignore my comments.
<S-tab> is an abomination. Modifier keys should be clearly separated
from function keys. <S-tab> to me means a key named "S-tab", not a key
named "tab" being modified by shift. S-<tab> means that!
substitute-command-keys and all other functions that print
human-readable key sequences, should put the angle brackets around the
SMALLEST possible string.
-- MJF
prev parent reply other threads:[~2006-09-18 4:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-17 17:22 substitute-command-keys to take optional `no-angles' arg? Drew Adams
2006-09-18 4:55 ` M Jared Finder [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
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='eel8sf$199$1@sea.gmane.org' \
--to=jared@hpalace.com \
/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).