From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: mail@daniel-mendler.de, larsi@gnus.org, stephen.berman@gmx.net,
monnier@iro.umontreal.ca, 61184@debbugs.gnu.org
Subject: bug#61184: 29.0.60; keymap-local-set and keymap-global-set became less strict
Date: Tue, 31 Jan 2023 18:06:11 +0200 [thread overview]
Message-ID: <83zg9y1yfg.fsf@gnu.org> (raw)
In-Reply-To: <87v8knng68.fsf@gmail.com> (message from Robert Pluim on Tue, 31 Jan 2023 11:37:19 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, Daniel Mendler
> <mail@daniel-mendler.de>, 61184@debbugs.gnu.org, Stefan Monnier
> <monnier@iro.umontreal.ca>, Eli Zaretskii <eliz@gnu.org>
> Date: Tue, 31 Jan 2023 11:37:19 +0100
>
> >>>>> On Tue, 31 Jan 2023 11:31:29 +0100, Stephen Berman <stephen.berman@gmx.net> said:
>
> >> (why *are* they different?)
>
> Stephen> 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.
>
> Stephen> Hm, I see just one space here with Emacs 29 and master (GNU/Linux)...
>
> including in a tty frame? I see one space in gui, two in
> tty. Redisplay expert to the white courtesy phone please.
You called?
That's a bug: two separate code paths that did equivalent jobs --
almost. Walking glyphs is a tricksy business...
Should be fixed now.
next prev parent reply other threads:[~2023-01-31 16:06 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
2023-01-31 10:37 ` Robert Pluim
2023-01-31 10:44 ` Stephen Berman
2023-01-31 16:06 ` Eli Zaretskii [this message]
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=83zg9y1yfg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61184@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mail@daniel-mendler.de \
--cc=monnier@iro.umontreal.ca \
--cc=rpluim@gmail.com \
--cc=stephen.berman@gmx.net \
/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).