[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#61184: 29.0.60; keymap-local-set and keymap-global-set became less s
From: |
Stephen Berman |
Subject: |
bug#61184: 29.0.60; keymap-local-set and keymap-global-set became less strict |
Date: |
Tue, 31 Jan 2023 11:31:29 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
On Tue, 31 Jan 2023 11:23:36 +0100 Robert Pluim <rpluim@gmail.com> wrote:
> (and redirecting back to bug#61184. EMORECOFFEE this morning)
>
>>>>>> On Tue, 31 Jan 2023 11:08:41 +0100, Stephen Berman
> <stephen.berman@gmx.net> said:
>
> >>
> >> 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')
>
> Stephen> TIL cursor-in-echo-area :-). This looks to me like a
> Stephen> good solution
>
> I looked at callint.c to figure out why `read-key-sequence' and
> (interactive "K") were different
Ah, ok.
> (why *are* they different?)
Good question.
> Stephen> (though aesthetically I would add a space after the colon in the
> Stephen> read-key-sequence-vector prompt, even though the user input
> doesn't
> Stephen> appear there).
>
> If you do that you get two spaces between the colon and the cursor.
Hm, I see just one space here with Emacs 29 and master (GNU/Linux)...
Steve Berman
bug#61184: 29.0.60; keymap-local-set and keymap-global-set became less strict, Eli Zaretskii, 2023/01/31