unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'netawater'" <netstandin-003@yahoo.com.cn>, <help-gnu-emacs@gnu.org>
Subject: RE: How to get current keymap
Date: Sat, 6 Dec 2008 22:35:18 -0800	[thread overview]
Message-ID: <003501c95835$f94bdfa0$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <873ah0v9j1.fsf@emacs.Arch.net>

> I want to get current mode's keymap, some modes do not have 
> keymap, but current keymap always exists. I need define a
> key for my function in it and my function
> can be always active for that mode.

If you want to define a key for only a specific (major or minor) mode, then use
that mode's keymap.

If that mode doesn't have a keymap, then it is less straightforward to define a
key for only that mode. You can define a key in some map that is accessible from
that keymap, so the key will be active in that mode, but then that key binding
will also hold outside that mode - unless you take pains to bind and unbind the
key when, say, the mode is entered and exited.

To see all maps accessible currently, you can use functions
`current-active-maps' and `accessible-keymaps'. See the Elisp manual, nodes
Active Keymaps and Scanning Keymaps.

Remember that there are several levels of priority for keymaps: minor mode maps
(in order), then (major mode) local map, then global map (and there are some
more levels). If you define a key in a local map, it's possible it gets shadowed
by a minor-mode binding. 

To make sense of what's happening, before you try to bind a key examine the
existing bindings in the current minor modes and major mode, as well as the
global bindings. Command `describe-keymap' (bound to `C-h M-k') in library
help-fns+.el shows you the bindings for a given map.
http://www.emacswiki.org/emacs/HelpPlus





  reply	other threads:[~2008-12-07  6:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-06 14:37 How to get current keymap netawater
2008-12-06 18:24 ` Xah Lee
2008-12-06 21:37 ` Rupert Swarbrick
2008-12-07  5:28   ` netawater
2008-12-07  6:35     ` Drew Adams [this message]
2008-12-07  6:49 ` Drew Adams
2008-12-07 15:09   ` Kevin Rodgers
2008-12-07 17:33     ` Drew Adams
     [not found]     ` <mailman.2157.1228671183.26697.help-gnu-emacs@gnu.org>
2008-12-08 14:39       ` netawater

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='003501c95835$f94bdfa0$0200a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=netstandin-003@yahoo.com.cn \
    /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.
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).