From: Lars Ingebrigtsen <larsi@gnus.org>
To: David Engster <deng@randomsample.de>
Cc: 5803@debbugs.gnu.org
Subject: bug#5803: 23.1.94; Using tq-enqueue in timer messes with keystroke echoing
Date: Tue, 08 Dec 2020 19:02:51 +0100 [thread overview]
Message-ID: <87h7owch10.fsf@gnus.org> (raw)
In-Reply-To: <87k4sulox8.fsf@engster.org> (David Engster's message of "Tue, 30 Mar 2010 00:54:11 +0200")
David Engster <deng@randomsample.de> writes:
> When using `tq-enqueue' in a timer, the keystroke echoing in the
> echo area becomes weird or is completely invisible. You should be able
> to reproduce this as follows:
>
> * emacs -Q
>
> * Evaluate the following:
>
> (setq proc (start-process "shell" (get-buffer-create "*process*") "/bin/sh"))
> (setq mytq (tq-create proc))
> (defun send-test ()
> (tq-enqueue mytq "echo TEST\n" "TEST[^0]*" nil nil))
> (setq timer (run-with-timer 1 1 'send-test))
>
> * Now hit 'C-x' and wait a second.
>
> * The string "C-x-" should appear in the echo area, but nothing can be
> seen.
(This bug report unfortunately got no response at the time.)
I can reproduce this in Emacs 28 with this small change:
(setq proc (start-process "shell" (get-buffer-create "*process*") "/bin/sh"))
(setq mytq (tq-create proc))
(defun send-test ()
(tq-enqueue mytq "echo TEST\n" "TEST[^0]*" nil 'ignore))
(setq timer (run-with-timer 1 1 'send-test))
I'm guessing this somehow interferes with the `echo-timeout' thing?
(Changing it to something shorter than 1 second makes the C-x-
appear... sometimes.)
Anybody got any insight into what might be happening here?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-12-08 18:02 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 [this message]
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
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
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=87h7owch10.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=5803@debbugs.gnu.org \
--cc=deng@randomsample.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).