From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 62207@debbugs.gnu.org, jonas@bernoul.li, larsi@gnus.org,
monnier@iro.umontreal.ca
Subject: bug#62207: 29.0.60; Trying to remove non-existent key binding instead adds a binding
Date: Fri, 17 Mar 2023 13:36:34 +0200 [thread overview]
Message-ID: <83mt4behj1.fsf@gnu.org> (raw)
In-Reply-To: <87edpnu2gk.fsf@gmail.com> (message from Robert Pluim on Fri, 17 Mar 2023 10:55:23 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: 62207@debbugs.gnu.org, larsi@gnus.org, jonas@bernoul.li, Stefan
> Monnier <monnier@iro.umontreal.ca>
> Date: Fri, 17 Mar 2023 10:55:23 +0100
>
> `keymap-unset' is also not documented in the lisp reference
> manual. How about this?
>
> @findex keymap-unset
> @defun keymap-unset keymap key &optional remove
> This function is the inverse of @code{keymap-set}, it unsets the
> binding for @var{key} in @var{keymap}, which is the same as setting
> the binding to @code{nil}. In order to instead remove the binding
> completely, specify @var{remove} as non-nil. This only makes a
> difference if @var{keymap} has a parent keymap. When unsetting a key
> in a child map, it will still shadow the same key in the parent
> keymap. Removing the binding will allow the key in the parent keymap
> to be used.
LGTM, thanks.
next prev parent reply other threads:[~2023-03-17 11:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 16:07 bug#62207: 29.0.60; Trying to remove non-existent key binding instead adds a binding Jonas Bernoulli
2023-03-15 16:51 ` Jonas Bernoulli
2023-03-15 17:36 ` Robert Pluim
2023-03-15 18:12 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-15 22:26 ` Jonas Bernoulli
2023-03-17 21:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-20 18:46 ` Jonas Bernoulli
2023-03-20 21:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-15 17:13 ` Eli Zaretskii
2023-03-15 17:39 ` Robert Pluim
2023-03-15 18:02 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-17 8:23 ` Eli Zaretskii
2023-03-17 8:54 ` Robert Pluim
2023-03-17 9:55 ` Robert Pluim
2023-03-17 11:36 ` Eli Zaretskii [this message]
2023-03-17 13:20 ` Robert Pluim
2023-03-17 11:32 ` Eli Zaretskii
2023-03-17 13:20 ` Robert Pluim
2023-03-20 18:14 ` Jonas Bernoulli
2023-03-17 20:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-18 5:51 ` Eli Zaretskii
2023-03-18 14:05 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-18 9:43 ` Robert Pluim
2023-03-18 14:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-20 9:09 ` Robert Pluim
2023-03-20 12:17 ` Eli Zaretskii
2023-03-20 15:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-20 15:27 ` Robert Pluim
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=83mt4behj1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62207@debbugs.gnu.org \
--cc=jonas@bernoul.li \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=rpluim@gmail.com \
/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.