unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Subject: Re: Rant: key sequences aren't specified in the elisp manual.
Date: Sun, 11 Dec 2005 00:03:50 -0500	[thread overview]
Message-ID: <E1ElJNG-0004BP-Jh@fencepost.gnu.org> (raw)
In-Reply-To: <Pine.LNX.3.96.1051117222258.317B-100000@acm.acm> (message from Alan Mackenzie on Thu, 17 Nov 2005 22:29:40 +0000 (GMT))

[I sent this message twice but did not get a response.]

I agree that there should be a node that describes key sequences.
I think the right place for it is under the Input Events node
in the file commands.texi.

It should describe both the Lisp representation of key sequences and
the various ways of writing them.  Since this is important, it is ok
to duplicate some of the material about key sequences in the Emacs
Manual.  The convenience would oughtweigh the duplication.

I am too overloaded to write one, though.  Could someone else try it?
Please ack this message if you do it.

      parent reply	other threads:[~2005-12-11  5:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17 22:29 Rant: key sequences aren't specified in the elisp manual Alan Mackenzie
2005-11-17 23:17 ` Edward O'Connor
2005-11-19 15:48   ` Portable key sequences [was: key sequences aren't specified...] Stephen J. Turnbull
2005-11-20 17:07     ` Portable key sequences Stefan Monnier
2005-11-17 23:19 ` Rant: key sequences aren't specified in the elisp manual Lennart Borgman
2005-11-17 23:19 ` Kevin Rodgers
2005-11-17 23:30   ` Drew Adams
2005-11-19 23:26 ` Richard M. Stallman
2005-11-27  0:31 ` Richard Stallman
2005-12-11  5:03 ` Richard Stallman [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=E1ElJNG-0004BP-Jh@fencepost.gnu.org \
    --to=rms@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).