From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 5803@debbugs.gnu.org, deng@randomsample.de
Subject: bug#5803: 23.1.94; Using tq-enqueue in timer messes with keystroke echoing
Date: Wed, 09 Dec 2020 19:42:59 +0100 [thread overview]
Message-ID: <87h7oux1l8.fsf@gnus.org> (raw)
In-Reply-To: <834kku6f0e.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 09 Dec 2020 19:55:13 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> When I run this, I get an error message about spurious
> communications. Does it work cleanly for you?
I get no errors when testing that code...
> Do we really need this tq package to reproduce the issue? It adds a
> layer of complexity to a scenario that is complex to begin with. I
> hope there can be a recipe that avoids using tq.
Yeah, the tq is unnecessary. The following reproduces for me:
(setq proc (start-process "shell" (get-buffer-create "*process*") "/bin/sh"))
(defun send-test ()
(process-send-string proc "ls /tmp\n"))
(setq timer (run-with-timer 1 1 'send-test))
I then hit
C-x
and I don't get the "C-x-" prompt.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-12-09 18:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 22:54 bug#5803: 23.1.94; Using tq-enqueue in timer messes with keystroke echoing David Engster
2020-12-08 18:02 ` Lars Ingebrigtsen
2020-12-08 18:37 ` Eli Zaretskii
2020-12-09 12:38 ` Lars Ingebrigtsen
2020-12-09 15:39 ` Eli Zaretskii
2020-12-09 17:55 ` Eli Zaretskii
2020-12-09 18:42 ` Lars Ingebrigtsen [this message]
2020-12-10 15:41 ` Eli Zaretskii
2020-12-10 17:29 ` Stefan Monnier
2020-12-10 18:20 ` Eli Zaretskii
2020-12-10 18:40 ` Stefan Monnier
2020-12-10 18:49 ` Eli Zaretskii
2020-12-11 7:26 ` Eli Zaretskii
2020-12-12 14:57 ` Stefan Monnier
2020-12-12 15:26 ` Lars Ingebrigtsen
2020-12-11 12:33 ` Lars Ingebrigtsen
2020-12-11 12:55 ` Eli Zaretskii
2020-12-17 16:36 ` bug#5803: " Platon Pronko
2020-12-23 12:35 ` Platon Pronko
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=87h7oux1l8.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=5803@debbugs.gnu.org \
--cc=deng@randomsample.de \
--cc=eliz@gnu.org \
/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.