unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Subject: discrepancy between read-key-sequence and manual
Date: Mon, 11 Sep 2006 15:42:19 +0200	[thread overview]
Message-ID: <85lkoqh64k.fsf@lola.goethe.zz> (raw)


(info "(elisp) Active Keymaps")

states:

   Normally the active keymaps are the `keymap' property keymap, the
   keymaps of any enabled minor modes, the current buffer's local
   keymap, and the global keymap, in that order.  Therefore, Emacs
   searches for each input key sequence in all these keymaps.  Here is
   a pseudo-Lisp description of how this process works:

     (or (if overriding-terminal-local-map
             (FIND-IN overriding-terminal-local-map)
           (if overriding-local-map
               (FIND-IN overriding-local-map)
             (or (FIND-IN (get-text-property (point) 'keymap))
                 (FIND-IN-ANY emulation-mode-map-alists)
                 (FIND-IN-ANY minor-mode-overriding-map-alist)
                 (FIND-IN-ANY minor-mode-map-alist)
                 (if (get-text-property (point) 'local-map)
                     (FIND-IN (get-text-property (point) 'local-map))
                   (FIND-IN (current-local-map))))))
         (FIND-IN (current-global-map)))

However, the code in read-key-sequence actually does

    (or (if (or overriding-terminal-local-map
                overriding-local-map)
            (or (FIND-IN overriding-terminal-local-map)
                (FIND-IN overriding-local-map))
           [...]

Namely, if overriding-terminal-local-map is present but no match is
found in it, overriding-local-map is also searched for a match.

Should the code be made to match the documentation, or the other way
round?

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

             reply	other threads:[~2006-09-11 13:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-11 13:42 David Kastrup [this message]
2006-09-11 14:20 ` discrepancy between read-key-sequence and manual Kim F. Storm
2006-09-11 14:25   ` David Kastrup
2006-09-11 19:58 ` Richard Stallman
2006-09-11 20:05   ` 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=85lkoqh64k.fsf@lola.goethe.zz \
    --to=dak@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).