[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Partly deferred font-locking?
From: |
Eli Zaretskii |
Subject: |
Re: Partly deferred font-locking? |
Date: |
Thu, 12 Jan 2023 17:51:03 +0200 |
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Date: Thu, 12 Jan 2023 15:33:03 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > > That would have to be done in Emacs, not in my code, right?
> >
> > Depends on whether the additional highlighting will be part of
> > jit-lock.el or not. The display engine only cares whether the value
> > of 'fontified' is nil or not.
>
> I can't image a solution that is not part of jit-lock.
>
> > while-no-input is not a way to interrupt an on-going calculation,
> > because it requires Emacs to check whether any input arrived, and
> > Emacs only does that when it's idle.
>
> Only when idle? Why is
>
> (while-no-input (while t (+ 1 1)))
>
> interruptable?
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.
- Re: Partly deferred font-locking?, (continued)
- Re: Partly deferred font-locking?, Ihor Radchenko, 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?, 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 <=
- Re: Partly deferred font-locking?, Michael Heerdegen, 2023/01/12