From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 21867@debbugs.gnu.org, zkanfer@gmail.com, Juri Linkov <juri@linkov.net>
Subject: bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands
Date: Wed, 07 Aug 2019 20:31:18 +0200 [thread overview]
Message-ID: <878ss496a1.fsf@mouse.gnus.org> (raw)
In-Reply-To: <jwvpnljihu6.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 05 Aug 2019 14:36:30 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Maybe rather than "during eval-last-sexp" we should say "during command
> execution" to try and be more vague (e.g. if it's done in
> post-command-hook, it's not done "during eval-last-sexp" but it's
> arguably still during "during command execution").
That makes sense. When I reintroduce the patch (after figuring out how
it broke macros) I'll change the text to that.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-08-07 18:31 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878ss496a1.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=21867@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=monnier@iro.umontreal.ca \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.