GNU bug report logs - #75933
29; Disabling smerge-command-prefix results in error

Previous Next

Full log

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

From: Daniel Colascione <dancol <at> dancol.org>
To: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of
 text editors" <bug-gnu-emacs <at> gnu.org>
Cc: Eli Zaretskii <eliz <at> gnu.org>, Jonas Bernoulli <jonas <at> bernoul.li>,
 75933 <at> debbugs.gnu.org, Stefan Monnier <monnier <at> iro.umontreal.ca>
Subject: Re: bug#75933: 29; Disabling smerge-command-prefix results in error
Date: Sat, 22 Feb 2025 18:10:36 -0500

Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org> writes:

>> Ping! How should we proceed with this issue?
>
> Maybe another way to look at it is that it's again bumping into
> `define-keymap`s limitation that you can't easily "deactivate"
> a binding.
>
> We saw that back in the bug#68213: if a keymap is defined where some of
> the key sequences are chosen dynamically (typically coming from a config
> var), we tend to get into trouble where it can be difficult/inconvenient
> to avoid duplicate key bindings (we fixed that problem by demoting that
> error to a warning), and similarly there's no easy way for the user to
> say "no key at all" (which was another way we could have fixed the
> problem in bug#68213).
>
> Maybe we should have an "impossible key sequence" (like we have the
> `regexp-unmatchable`) and offer it in the customization interface?

The question is ill-formed. Why do we have keymaps with bindings based
on random defcustoms in the first place? The proper place to customize a
keymap is the keymap. 

Previous Next

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