[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 29.0.60; keymap-local-set and keymap-global-set became less strict

From: Stephen Berman
Subject: Re: 29.0.60; keymap-local-set and keymap-global-set became less strict
Date: Tue, 31 Jan 2023 11:08:41 +0100
User-agent: Gnus/5.13 (Gnus v5.13)

On Tue, 31 Jan 2023 10:05:15 +0100 Robert Pluim <rpluim@gmail.com> wrote:

> Dropping bug-gnu-emacs, adding emacs-devel
>>>>>> On Tue, 31 Jan 2023 04:42:25 +0100, Lars Ingebrigtsen <larsi@gnus.org> 
>>>>>> said:
>     Lars> In addition, having one single syntax allows people to grep for 
> bindings
>     Lars> etc -- when exploring the source code, they can isearch for `C-c 
> C-k'
>     Lars> (or whatever) exactly and reliably find the command they're looking 
> for
>     Lars> that way (eventually).
> We have bindings in emacs currently that are Not Compliant™, thatʼs
> for sure.
>     Lars> So keymap-local-set and keymap-global-set should be fixed to be 
> strict
>     Lars> again, otherwise there's not much point to the entire `keymap-*'
>     Lars> exercise.
> OK. How about this then (why are the `cursor-in-echo-area' shenanigans
> necessary? I wonder if thatʼs a bug, since without them we either get
> the cursor not showing in the minibuffer for
> `read-key-sequence-vector', or we get an extra space displayed by
> `read-command')

TIL cursor-in-echo-area :-).  This looks to me like a good solution
(though aesthetically I would add a space after the colon in the
read-key-sequence-vector prompt, even though the user input doesn't
appear there).

Steve Berman

reply via email to

[Prev in Thread] Current Thread [Next in Thread]