unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: herring@lanl.gov
Cc: emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
	rms@gnu.org, "Kim F. Storm" <storm@cua.dk>
Subject: Re: `key-binding' and XEmacs-style events
Date: Fri, 02 Mar 2007 09:31:41 +0100	[thread overview]
Message-ID: <85y7mg9hci.fsf@lola.goethe.zz> (raw)
In-Reply-To: <38780.128.165.123.18.1172793133.squirrel@webmail.lanl.gov> (Stuart D. Herring's message of "Thu\, 1 Mar 2007 15\:52\:13 -0800 \(PST\)")

"Stuart D. Herring" <herring@lanl.gov> writes:

>>> We're talking about going the other way -- supporting (key-binding
>>> [(?a)])
>>> in Emacs
>>
>> Yes, but we don't have to fix it.
>>
>> If you want to write portable code, simply use the GNU Emacs format [?a],
>> as this is also supported by XEmacs.
>
> What I am actually interested in can be seen at
> http://www.emacswiki.org/cgi-bin/wiki/unbound.el: this code
> mechanically manipulates keystrokes.  By far the easiest way to do
> this is to generate XEmacs lists with modifiers and base events,
> rather than having to generate the symbol 'C-end and the low-ASCII
> ?\C-a and the high-bit-set ?\C-` with separate rules.  Then the
> natural way of representing an unmodified key is a list containing 0
> modifiers and the base event, but that fails (for `key-binding'
> only; `lookup-key' and `define-key' accept it) because it doesn't
> happen to begin with a symbol.

Is it documented anywhere that this a valid way to create a key
sequence with modifiers?

Should we document it?

Should we change EVENT_HAS_PARAMETERS itself maybe?  Or EVENTP?

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2007-03-02  8:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-28 22:57 `key-binding' and XEmacs-style events Stuart D. Herring
2007-03-01  8:14 ` Richard Stallman
2007-03-01 15:19   ` Stefan Monnier
2007-03-01 22:27     ` Stuart D. Herring
2007-03-01 23:35       ` Kim F. Storm
2007-03-01 23:52         ` Stuart D. Herring
2007-03-02  8:31           ` David Kastrup [this message]
2007-03-04  6:13             ` Stuart D. Herring
2007-03-02  8:26       ` Richard Stallman
2007-03-02  8:46         ` David Kastrup
2007-03-02 23:46           ` Richard Stallman
2007-03-03  7:40             ` David Kastrup
2007-03-04  2:00               ` Richard Stallman
2007-03-04  6:27                 ` Stuart D. Herring
2007-03-06 17:06           ` Stuart D. Herring
2007-03-02  8:28       ` David Kastrup
2007-03-02  3:28     ` Richard Stallman

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=85y7mg9hci.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=herring@lanl.gov \
    --cc=monnier@iro.umontreal.ca \
    --cc=rms@gnu.org \
    --cc=storm@cua.dk \
    /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).