From: Ihor Radchenko <yantar92@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael_heerdegen@web.de, emacs-devel@gnu.org
Subject: Re: Partly deferred font-locking?
Date: Thu, 12 Jan 2023 14:44:11 +0000 [thread overview]
Message-ID: <87ilhb95j8.fsf@localhost> (raw)
In-Reply-To: <837cxrbz1r.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> I just tried
>>
>> (while-no-input (let ((x 0)) (while t (cl-incf x) (when (> 3 (random 1000000)) (message "%d" x)))))
>>
>> and it does not block.
>
> Do you understand why? Specifically: which code in Emacs caused us to
> throw on input in this case? And is that going to happen when Emacs
> calls a C function that hits the disk?
AFAIU, maybe_quit throws the necessary signal as needed.
For external C functions that interact with disk, they will indeed not
produce the signal. However, the signal will likely be thrown soon after
disk interaction ends. In my experience, helm command that opens a
number of files is successfully interrupted after populating a file
buffer but before initializing the major mode.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-01-12 14:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 17:15 Partly deferred font-locking? Michael Heerdegen
2023-01-11 17:43 ` [External] : " Drew Adams
2023-01-11 18:33 ` Michael Heerdegen
2023-01-11 18:38 ` Drew Adams
2023-01-11 18:49 ` Drew Adams
2023-01-11 19:31 ` Michael Heerdegen
2023-01-11 17:45 ` Eli Zaretskii
2023-01-11 18:36 ` Michael Heerdegen
2023-01-11 19:58 ` Eli Zaretskii
2023-01-12 13:14 ` Michael Heerdegen
2023-01-12 13:45 ` Eli Zaretskii
2023-01-12 14:00 ` Michael Heerdegen
2023-01-12 14:13 ` Eli Zaretskii
2023-01-12 14:26 ` Ihor Radchenko
2023-01-12 14:30 ` Ihor Radchenko
2023-01-12 14:36 ` Eli Zaretskii
2023-01-12 14:44 ` Ihor Radchenko [this message]
2023-01-12 15:11 ` Eli Zaretskii
2023-01-12 15:40 ` Ihor Radchenko
2023-01-12 14:30 ` Eli Zaretskii
2023-01-12 14:36 ` Ihor Radchenko
2023-01-12 14:38 ` Michael Heerdegen
2023-01-12 14:33 ` Michael Heerdegen
2023-01-12 15:51 ` Eli Zaretskii
2023-01-12 16:02 ` Michael Heerdegen
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=87ilhb95j8.fsf@localhost \
--to=yantar92@posteo.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.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).