GNU bug report logs - #62207
29.0.60; Trying to remove non-existent key binding instead adds a binding

Previous Next

Full log

Message #41 received at 62207 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Robert Pluim <rpluim <at> gmail.com>
Cc: 62207 <at> debbugs.gnu.org, jonas <at> bernoul.li, larsi <at> gnus.org,
 monnier <at> iro.umontreal.ca
Subject: Re: 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

> From: Robert Pluim <rpluim <at> gmail.com>
> Cc: 62207 <at> debbugs.gnu.org,  larsi <at> gnus.org,  jonas <at> bernoul.li,  Stefan
>  Monnier <monnier <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.