From: PPAATT@aol.com
Cc: emacs-devel@gnu.org
Subject: Re: bindings reserved for users
Date: Thu, 18 Apr 2002 16:47:37 EDT [thread overview]
Message-ID: <30.25761a54.29f08ae9@aol.com> (raw)
> > > ( C-h i m emacs RET m keymaps RET )
> > > ... As a user, you can redefine any key;
> > > but it might be best to stick to key
> > > sequences that consist of `C-c'
> > > followed by a letter
...
> > followed by a (lowercase or uppercase) letter.
...
> I was confused about this issue ...
Me too.
From context I understood this English was meant to be restricted to only
letters that happen to appear as labels of keys of an actual keyboard.
(True/false?)
Here that means QWERTYUIOP ASDFGHJKLÑ ZXCVBNMÇ. That is, the [A-Z] of an
English keyboard plus Ñ and Ç (i.e. add English N with ~ tilde above and add
English C with , cedilla below).
By associating GNU Emacs with Massachusetts I was able to guess further that
the meaning here was the more restrictive [a-zA-Z] or [a-z], but as yet I'm
too stunningly ignorant of Emacs to know how to resolve this ambiguity over
upper/lower case myself.
As we speak, gnu.emacs.help folk at
http://groups.google.com/groups?as_usubject=Insert%20key%20should%20be
are busy explaining to me that C-h b describe-bindings is not a good way for
me to try and predict C-h k describe-key results.
Also that I can't reasonably expect a computer to know what kind of keyboard
is connected to it.
To my ignorant eye, C-h k describe-key claims like:
overwrite-mode is on insert
C-c C-h is undefined
appear to be lies.
I have no Insert key, and C-c C-h is the only technique I've found yet for
listing what key sequences prefixed by C-c are bound for me by default.
gnu.emacs.help folk are working to clue me in.
> http://members.aol.com/plforth/moforth/index.html
> http://members.aol.com/plforth/moforth/20020325/ofemacs.txt
I'm returning to Emacs after an eight year absence, because I need a
reasonably capable source code editor to run inside Apple OpenFirmware boot
Forth.
> an eight year absence
http://members.aol.com/plscsi/emacs/emacs-deja-vu.html
Pat LaVarre
next reply other threads:[~2002-04-18 20:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 20:47 PPAATT [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-26 15:30 bindings reserved for users PPAATT
2002-04-26 15:45 ` Stefan Monnier
2002-04-24 12:45 PPAATT
2002-04-23 13:47 PPAATT
2002-04-21 13:49 PPAATT
2002-04-22 7:47 ` Richard Stallman
2002-04-22 9:32 ` Stefan Monnier
2002-04-20 12:13 PPAATT
2002-04-17 14:14 Kai Großjohann
2002-04-18 18:44 ` Richard Stallman
2002-04-18 19:37 ` Kai Großjohann
2002-04-20 17:28 ` Richard Stallman
2002-04-22 11:29 ` Kai Großjohann
2002-04-22 18:34 ` Eli Zaretskii
2002-04-22 20:10 ` Simon Josefsson
2002-04-23 6:49 ` Eli Zaretskii
2002-04-23 19:29 ` Richard Stallman
2002-04-25 6:05 ` Richard Stallman
2002-04-25 11:13 ` Eli Zaretskii
2002-04-26 8:52 ` Florian Weimer
2002-04-23 10:48 ` Kai Großjohann
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=30.25761a54.29f08ae9@aol.com \
--to=ppaatt@aol.com \
--cc=emacs-devel@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 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).