From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Cc: Daniel Mendler <mail@daniel-mendler.de>
Subject: Re: [elpa] externals/cape 45fe322c99: cape-company-to-capf: Remove (t . cape--done) from unread-command-events (Fix #23)
Date: Sat, 15 Jan 2022 10:44:23 -0500 [thread overview]
Message-ID: <jwvfsppj9hi.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20220115145717.E3D2BC0DA2E@vcs2.savannah.gnu.org> (ELPA Syncer's message of "Sat, 15 Jan 2022 09:57:17 -0500 (EST)")
> + ;; XXX NOTE: For some reason Emacs sometimes converts
> + ;; cape--done to (t . cape--done).
`unread-command-events` is pretty tricky/nasty to get right.
So I'm not sure if what you see is normal or is a bug.
This said, the docstring says:
Events read from this list are not normally added to ‘this-command-keys’,
as they will already have been added once as they were read for the first time.
An element of the form (t . EVENT) forces EVENT to be added to that list.
An element of the form (no-record . EVENT) means process EVENT, but do not
record it in the keyboard macros, recent-keys, and the dribble file.
So it sounds like (t . cape--done) would be an error, given that I can't
think of a good reason why we'd want to add the pseudo-event `cape--done`
to `this-command-keys`.
So, if you can find a recipe to reproduce the problem, it would be good
to report it as a bug (see how it's used in async-style code with
a `sit-for` loop, I expect it'll be nasty to reproduce and even worse
to debug).
Stefan
parent reply other threads:[~2022-01-15 15:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220115145717.E3D2BC0DA2E@vcs2.savannah.gnu.org>]
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=jwvfsppj9hi.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=mail@daniel-mendler.de \
/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).