From: Tim Cross <theophilusx@gmail.com>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
schwab@linux-m68k.org, drew.adams@oracle.com,
emacs-devel@gnu.org
Subject: Re: Why all the Alt bindings by default?
Date: Thu, 27 Oct 2011 16:35:31 +1100 [thread overview]
Message-ID: <CAC=50j_ZN0Jsw2F4-Syfx8vdn5y9Tvd2oXndCifY54vbKK8W9g@mail.gmail.com> (raw)
In-Reply-To: <87ty6vox33.fsf@uwakimon.sk.tsukuba.ac.jp>
On Thu, Oct 27, 2011 at 3:52 PM, Stephen J. Turnbull <stephen@xemacs.org> wrote:
> Tim Cross writes:
>
> > The other question is if I have defined some real alt bindings, how
> > do you tell those form key translations?
>
> In what context? If you're a user looking at the C-h b buffer,
> heuristically: non-ASCII single characters are not command bindings,
> they're keyboard translations. In a program, you'll use different
> APIs to access them, so one can hardly be mistaken for the other.
>
Yes, but is that reasonable in the context of a new user who is likely
using C-h b to identify and learn about available key bindings? It
would seem a reasonable assumption that when you use a command which
is supposed to describe key bindings, what that command shows is key
bindings and not key bindings and key translations.
The doc string for the command doesn't mention anything about key
translations. Nor does there seem to be much in the emacs manual.
Perhaps all that is required is for this to be added to the doc
string. I think this would then largely reduce the issue to minor
annoyance at the list of key bindings including data I'm probably not
interested in and didn't ask for.
Tim
--
Tim Cross
next prev parent reply other threads:[~2011-10-27 5:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 16:50 Why all the Alt bindings by default? Drew Adams
2011-10-26 17:02 ` Andreas Schwab
2011-10-26 17:13 ` Drew Adams
2011-10-26 19:16 ` Andreas Schwab
2011-10-26 20:20 ` Drew Adams
2011-10-26 21:35 ` Tim Cross
2011-10-27 1:48 ` Stephen J. Turnbull
2011-10-27 2:05 ` Tim Cross
2011-10-27 4:07 ` Eli Zaretskii
2011-10-27 4:14 ` Tim Cross
2011-10-27 4:52 ` Stephen J. Turnbull
2011-10-27 5:35 ` Tim Cross [this message]
2011-10-27 8:24 ` Eli Zaretskii
2011-10-27 12:19 ` Tim Cross
2011-10-27 15:17 ` Drew Adams
2011-10-27 15:33 ` Andreas Schwab
2011-10-27 15:43 ` Drew Adams
2011-10-27 15:51 ` Andreas Schwab
2011-10-27 16:06 ` Drew Adams
2011-10-27 12:28 ` Stefan Monnier
2011-10-27 15:20 ` Drew Adams
2011-10-28 0:25 ` Stefan Monnier
2011-10-26 17:52 ` Stefan Monnier
2011-10-26 18:03 ` Drew Adams
2011-10-26 18:22 ` Eli Zaretskii
2011-10-26 20:14 ` 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
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='CAC=50j_ZN0Jsw2F4-Syfx8vdn5y9Tvd2oXndCifY54vbKK8W9g@mail.gmail.com' \
--to=theophilusx@gmail.com \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.org \
--cc=stephen@xemacs.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 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).