unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: A bug, I think, in key-binding
Date: Wed, 09 Aug 2006 01:18:11 -0400	[thread overview]
Message-ID: <87y7tysd7e.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1GAg9S-0003XD-EU@fencepost.gnu.org> (Richard Stallman's message of "Wed, 09 Aug 2006 00:58:42 -0400")

> That is true.  But I think key-binding MUST do what it now does.
> That is an essential primitive for accessing keymaps.

I don't think the two are incompatible: currently, key-binding does not work
if one of the keys in the sequence is an event (rather than just a char or
a symbol), so we would just need to extend it so it also works with events.

The only trick might be to distinguish events from Lucid-style key
specs like (control c).

> Perhaps we should have a function to do lookup on a key sequence
> just the same way the command loop does.  That can be written in Lisp;
> it just has to see if the first event is a mouse even, and move point
> there inside save-excursion.

Moving point is not sufficient if the click is on an image-map, or on
before-string.  I'd rather reuse the C code if at all possible rather than
try to mimick it in elisp (unless we can completely replace the C version
with the elisp version).


        Stefan

  reply	other threads:[~2006-08-09  5:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08 22:47 A bug, I think, in key-binding David Kastrup
2006-08-09  4:58 ` Richard Stallman
2006-08-09  5:18   ` Stefan Monnier [this message]
2006-08-10  1:13     ` Richard Stallman
2006-08-17  6:02     ` Richard Stallman
2006-08-17 14:48       ` Stefan Monnier
2006-08-18 15:47         ` Richard Stallman
2006-08-18 11:02       ` David Kastrup
2006-08-22 15:41         ` Richard Stallman
2006-08-22 16:39           ` David Kastrup
2006-08-09  7:03   ` David Kastrup

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=87y7tysd7e.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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).