[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Partly deferred font-locking?
From: |
Michael Heerdegen |
Subject: |
Re: Partly deferred font-locking? |
Date: |
Thu, 12 Jan 2023 17:02:21 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Eli Zaretskii <eliz@gnu.org> writes:
> [...]
Thanks to you two for elaborating.
> Yes, the Lisp interpreter also tests for input in many places. But if
> you call a C library function, that won't happen until it returns.
I did not expect that (or have already learned it). It is not such a
big problem for what we discuss IME. Unless maybe in cases where a disk needs
to spin up or so - but that blocks other things as font-lock (command
loop) as well.
Michael.
- Re: Partly deferred font-locking?, (continued)
- Re: Partly deferred font-locking?, Ihor Radchenko, 2023/01/12
- Re: Partly deferred font-locking?, Eli Zaretskii, 2023/01/12
- Re: Partly deferred font-locking?, Ihor Radchenko, 2023/01/12
- Re: Partly deferred font-locking?, Eli Zaretskii, 2023/01/12
- Re: Partly deferred font-locking?, Ihor Radchenko, 2023/01/12
- Re: Partly deferred font-locking?, Eli Zaretskii, 2023/01/12
- Re: Partly deferred font-locking?, Ihor Radchenko, 2023/01/12
- Re: Partly deferred font-locking?, Michael Heerdegen, 2023/01/12
- Re: Partly deferred font-locking?, Michael Heerdegen, 2023/01/12
- Re: Partly deferred font-locking?, Eli Zaretskii, 2023/01/12
- Re: Partly deferred font-locking?,
Michael Heerdegen <=