[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Reliable after-change-functions (via: Using incremental parsing in E

From: 조성빈
Subject: Re: Reliable after-change-functions (via: Using incremental parsing in Emacs)
Date: Wed, 1 Apr 2020 03:42:31 +0900

> 2020. 4. 1. 오전 2:53, Eli Zaretskii <address@hidden> 작성:
>> From: Stefan Monnier <address@hidden>
>> Cc: address@hidden,  address@hidden,  address@hidden
>> Date: Tue, 31 Mar 2020 13:10:27 -0400
>>>> How large is "very large" here?
>>> xdisp.c comes to mind, obviously.
>> I'd expect tree-sitter to be able to parse xdisp.c in one second or less.
> One second of delay before the first window-full is displayed?  This
> is like infinity.

Maybe I misunderstood, or maybe it’s just b.c. I don’t know enough internals, 
but doesn’t Emacs just display the raw text until highlighting is finished? It 
wouldn’t be an experience of not seeing the text for a sec, it would be more of 
a see the text and highlights are applied later.  

> And you didn't account for the time to take buffer-string of the
> entire buffer (which involves allocating a large chunk of memory),
> then encode it in UTF-8 (which needs to allocate another chunk of
> memory), and pass that to tree-sitter.  If that's what the current
> interface does.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]