From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org, no-spam@cua.dk
Subject: Re: Using multiple minor-mode keymaps.
Date: Mon, 11 Mar 2002 12:05:55 -0700 (MST) [thread overview]
Message-ID: <200203111905.g2BJ5t904555@wijiji.santafe.edu> (raw)
In-Reply-To: <20020310.201856.01365645.Takaaki.Ota@am.sony.com> (message from Tak Ota on Sun, 10 Mar 2002 20:18:56 -0800 (PST))
The `keymap' property is used for overriding just *part* of the local
map. For most uses, `keymap' is better. I am not sure if there is
still any good reason to use `local-map'.
I rewrote the text in the manual as follows:
@item keymap
@cindex keymap of character
@kindex keymap @r{(text property)}
The @code{keymap} property specifies an additional keymap for
commands. The property's value for the character after point, if
non-@code{nil}, is used for key lookup before the buffer's local map.
(For mouse clicks, the @code{keymap} property of the character clicked
on is the one used.) If the property value is a symbol, the symbol's
function definition is used as the keymap. @xref{Active Keymaps}.
@item local-map
@kindex local-map @r{(text property)}
This property specifies a keymap to use @emph{instead of} the buffer's
local map. If the property value is a symbol, the symbol's function
definition is used as the keymap. For most purposes (perhaps all
purposes), the @code{keymap} is superior.
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
prev parent reply other threads:[~2002-03-11 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5xg039mks5.fsf@kfs2.cua.dk>
[not found] ` <20020309.200417.107712392.Takaaki.Ota@am.sony.com>
[not found] ` <5xwuwkw5sa.fsf@kfs2.cua.dk>
2002-03-11 4:18 ` Using multiple minor-mode keymaps Tak Ota
2002-03-11 19:05 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200203111905.g2BJ5t904555@wijiji.santafe.edu \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=no-spam@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.