From: Stephen Berman <stephen.berman@gmx.net>
To: Robert Pluim <rpluim@gmail.com>
Cc: Daniel Mendler <mail@daniel-mendler.de>,
Lars Ingebrigtsen <larsi@gnus.org>,
61184@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
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 [thread overview]
Message-ID: <87wn53m1vi.fsf@rub.de> (raw)
In-Reply-To: <877cx3ovdj.fsf@gmail.com> (Robert Pluim's message of "Tue, 31 Jan 2023 11:23:36 +0100")
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
next prev parent reply other threads:[~2023-01-31 10:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 20:52 bug#61184: 29.0.60; keymap-local-set and keymap-global-set became less strict Daniel Mendler
2023-01-30 21:00 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-30 21:06 ` Daniel Mendler
2023-01-30 21:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-30 22:03 ` Daniel Mendler
2023-01-31 3:42 ` Lars Ingebrigtsen
[not found] ` <87zg9zvzuc.fsf@gmail.com>
[not found] ` <871qnbnhhy.fsf@rub.de>
2023-01-31 10:23 ` Robert Pluim
2023-01-31 10:31 ` Stephen Berman [this message]
2023-01-31 10:37 ` Robert Pluim
2023-01-31 10:44 ` Stephen Berman
2023-01-31 16:06 ` Eli Zaretskii
2023-01-31 12:10 ` Eli Zaretskii
2023-01-31 12:49 ` Daniel Mendler
2023-01-31 14:16 ` Eli Zaretskii
2023-01-31 14:53 ` Daniel Mendler
2023-02-03 9:19 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wn53m1vi.fsf@rub.de \
--to=stephen.berman@gmx.net \
--cc=61184@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=mail@daniel-mendler.de \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).