From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21867@debbugs.gnu.org, zkanfer@gmail.com
Subject: bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands
Date: Thu, 01 Aug 2019 21:25:49 +0200 [thread overview]
Message-ID: <87k1bwg01u.fsf@mouse.gnus.org> (raw)
In-Reply-To: <83lfwcheyy.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 01 Aug 2019 22:18:13 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Lars Ingebrigtsen <larsi@gnus.org>
>> Cc: 21867@debbugs.gnu.org, zkanfer@gmail.com
>> Date: Thu, 01 Aug 2019 20:58:50 +0200
>>
>> >> What `read-char' comes under "input keystrokes", I guess?
>> >
>> > Yes.
>>
>> Right, but view-lossage currently says
>>
>> C-x C-e ;; eval-last-sexp
>> a C-h l ;; view-lossage
>>
>> which is a very curious way of displaying this. It makes it look like
>> "a C-h l" is a key stroke.
>
> A newline should be enough to fix that, I think.
Yes, that'd be OK, I think, but it means that we have to
put... something... into the recent_keys variable to mark the "a" as
having been read by `read-string'. I suggested (nil . "some-string"),
but perhaps just (nil) would be OK?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-08-01 19:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 4:58 bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands Zachary Kanfer
2019-08-01 18:05 ` Lars Ingebrigtsen
2019-08-01 18:21 ` Eli Zaretskii
2019-08-01 18:41 ` Lars Ingebrigtsen
2019-08-01 18:51 ` Eli Zaretskii
2019-08-01 18:58 ` Lars Ingebrigtsen
2019-08-01 19:18 ` Eli Zaretskii
2019-08-01 19:25 ` Lars Ingebrigtsen [this message]
2019-08-02 6:41 ` Eli Zaretskii
2019-08-02 11:19 ` Lars Ingebrigtsen
2019-08-02 12:02 ` Eli Zaretskii
2019-08-02 20:16 ` Stefan Monnier
2019-08-03 12:13 ` Lars Ingebrigtsen
2019-08-03 21:07 ` Stefan Monnier
2019-08-03 21:14 ` Lars Ingebrigtsen
2019-08-03 21:49 ` Juri Linkov
2019-08-04 11:45 ` Lars Ingebrigtsen
2019-08-04 21:04 ` Juri Linkov
2019-08-04 12:54 ` Stefan Monnier
2019-08-04 19:44 ` Juri Linkov
2019-08-05 18:36 ` Stefan Monnier
2019-08-07 18:31 ` Lars Ingebrigtsen
2019-08-23 1:41 ` Lars Ingebrigtsen
2019-08-05 9:15 ` Lars Ingebrigtsen
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=87k1bwg01u.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=21867@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=zkanfer@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).