From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: mwd@md5i.com, stephen_leake@stephe-leake.org, mwd@cert.org,
emacs-devel@gnu.org
Subject: Re: emacs-tree-sitter and Emacs
Date: Thu, 02 Apr 2020 21:29:48 +0300 [thread overview]
Message-ID: <83blo9yc4j.fsf@gnu.org> (raw)
In-Reply-To: <C02E3CD8-E30F-4B79-9F15-9D9FC2CE227C@gmail.com> (message from Yuan Fu on Thu, 2 Apr 2020 13:18:51 -0400)
> From: Yuan Fu <casouri@gmail.com>
> Date: Thu, 2 Apr 2020 13:18:51 -0400
> Cc: Eli Zaretskii <eliz@gnu.org>,
> mwd@md5i.com,
> stephen_leake@stephe-leake.org,
> emacs-devel@gnu.org
>
> Can we do something similar to fontified text property? I.e., only parse the first screen full of text when a buffer is opened, and mark the rest as unparsed with text property. Then when we need to access the parse tree (for fortification, etc), send all unparsed text before some point (e.g., last visible char in the window) to the parser.
The current "parser" used by font-lock is used exactly in this fashion
from the display engine, IIUC what you mean.
next prev parent reply other threads:[~2020-04-02 18:29 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 3:23 emacs-tree-sitter and Emacs Jorge Javier Araya Navarro
2020-03-30 13:07 ` Eli Zaretskii
2020-03-30 14:00 ` Stefan Monnier
2020-04-01 0:08 ` Stephen Leake
2020-04-01 0:27 ` Stephen Leake
2020-04-01 13:20 ` Eli Zaretskii
2020-04-01 19:51 ` Stephen Leake
2020-04-02 14:03 ` Eli Zaretskii
2020-04-02 14:27 ` Michael Welsh Duggan
2020-04-02 15:15 ` Eli Zaretskii
2020-04-02 15:24 ` Michael Welsh Duggan
2020-04-02 16:10 ` Eli Zaretskii
2020-04-02 16:19 ` Michael Welsh Duggan
2020-04-02 17:18 ` Yuan Fu
2020-04-02 17:39 ` Stefan Monnier
2020-04-02 18:17 ` Yuan Fu
2020-04-02 18:26 ` Stefan Monnier
2020-04-03 2:16 ` Stephen Leake
2020-04-02 18:29 ` Eli Zaretskii [this message]
2020-04-02 18:27 ` Eli Zaretskii
2020-04-02 18:50 ` Michael Welsh Duggan
2020-04-02 19:03 ` Eli Zaretskii
2020-04-02 19:39 ` 조성빈
2020-04-03 6:37 ` Eli Zaretskii
2020-04-03 17:27 ` Stephen Leake
2020-04-02 19:48 ` Stefan Monnier
2020-04-03 2:06 ` Stephen Leake
2020-04-03 7:33 ` Eli Zaretskii
2020-04-03 17:24 ` Stephen Leake
2020-04-03 18:39 ` Eli Zaretskii
2020-04-02 15:33 ` martin rudalics
2020-04-03 1:55 ` Stephen Leake
2020-04-03 4:47 ` Jorge Javier Araya Navarro
2020-04-03 7:32 ` Eli Zaretskii
2020-04-03 17:05 ` Stephen Leake
2020-04-03 18:19 ` Eli Zaretskii
2020-04-04 0:00 ` Stephen Leake
2020-04-01 13:28 ` Stefan Monnier
2020-03-30 14:11 ` Stefan Monnier
2020-03-30 17:00 ` Jorge Javier Araya Navarro
2020-03-30 17:07 ` Dmitry Gutov
2020-03-30 17:09 ` Jorge Javier Araya Navarro
2020-03-30 17:22 ` Stefan Monnier
2020-03-30 17:34 ` Jorge Javier Araya Navarro
2020-03-30 17:50 ` Stefan Monnier
2020-04-01 0:30 ` Stephen Leake
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83blo9yc4j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mwd@cert.org \
--cc=mwd@md5i.com \
--cc=stephen_leake@stephe-leake.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.