From: Shane Mulligan <mullikine@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 48500@debbugs.gnu.org
Subject: bug#48500: 28.0.50; url-retrieve-synchronously exits abnormally due to pending keyboard input from terminal
Date: Thu, 20 May 2021 01:12:10 +1200 [thread overview]
Message-ID: <CACT87JqwLHqHZHtBU5xkxe46r_w3jxB-jq32x7XhN0+GP0ddvg@mail.gmail.com> (raw)
In-Reply-To: <835yzfq6lm.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]
I will do some further studies to see if I can find exactly how quit is
being generated.
Shane Mulligan
How to contact me:
🇦🇺 00 61 421 641 250
🇳🇿 00 64 21 1462 759 <+64-21-1462-759>
mullikine@gmail.com
On Wed, May 19, 2021 at 11:57 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Shane Mulligan <mullikine@gmail.com>
> > Date: Wed, 19 May 2021 18:48:09 +1200
> >
> > I may have resolved this issue with the following patch to
> `url-retrieve-synchronously`.
> > What this achieves is to trigger a `quit` in a controlled environment
> rather than allowing it to occur when
> > `accept-process-output` is run.
> > It's not always wanted to trigger a quit when `(input-pending-p)` is
> `t`. But I noticed from placing
> > `while-no-input` around `accept-process-output` to avoid the `quit` that
> `url-retrieve-synchronously` would
> > then hang but with the controlled `quit` happening beforehand,
> `accept-process-output` no longer needs
> > `while-no-input` around it. The end result is buttery smooth helm with
> no accidental `quit` from typing too
> > fast. I think this may have resulted in GUI helm faster too.
>
> Thanks, but what causes a quit in the first place?
>
[-- Attachment #2: Type: text/html, Size: 3102 bytes --]
next prev parent reply other threads:[~2021-05-19 13:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 6:35 bug#48500: 28.0.50; url-retrieve-synchronously exits abnormally due to pending keyboard input from terminal Shane Mulligan
2021-05-18 15:05 ` Eli Zaretskii
[not found] ` <CACT87JpYLto5_HY8V=9+R3uvC614BxB_H_6gduW7hwnoJL1PDA@mail.gmail.com>
2021-05-18 16:54 ` Eli Zaretskii
2021-05-18 23:32 ` Shane Mulligan
2021-05-19 6:48 ` Shane Mulligan
2021-05-19 6:49 ` Shane Mulligan
2021-05-19 11:46 ` Shane Mulligan
2021-05-19 11:57 ` Eli Zaretskii
[not found] ` <CACT87JrC=pzVBJXLGP9k22OCnXTd0_3SYimsiD=AX9A7QsJS2A@mail.gmail.com>
2021-05-19 13:08 ` bug#48500: Fwd: " Shane Mulligan
2021-05-19 13:12 ` Shane Mulligan [this message]
2021-05-20 23:35 ` Shane Mulligan
2022-07-13 11:58 ` Lars Ingebrigtsen
2022-08-12 15:57 ` 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=CACT87JqwLHqHZHtBU5xkxe46r_w3jxB-jq32x7XhN0+GP0ddvg@mail.gmail.com \
--to=mullikine@gmail.com \
--cc=48500@debbugs.gnu.org \
--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 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).