From: Eli Zaretskii <eliz@gnu.org>
To: Ivan Yonchovski <yyoncho@gmail.com>
Cc: 42028@debbugs.gnu.org
Subject: bug#42028: [Feature Request] 27.0.91; Provide the ability dynamic modules to post events in emacs event loop
Date: Wed, 24 Jun 2020 21:04:52 +0300 [thread overview]
Message-ID: <83y2ocs5kr.fsf@gnu.org> (raw)
In-Reply-To: <874kr0gyhi.fsf@gmail.com> (message from Ivan Yonchovski on Wed, 24 Jun 2020 20:33:29 +0300)
> From: Ivan Yonchovski <yyoncho@gmail.com>
> Cc: 42028@debbugs.gnu.org
> Date: Wed, 24 Jun 2020 20:33:29 +0300
>
> > You cannot easily post to the queue from a worker thread, because the
> > queue cannot be posted to asynchronously.
>
> AFAIK this is not possible at all - thus this feature request.
Your feature just asked for a way to queue events, it didn't say
anything about doing that asynchronously, not from a function invoked
by the main thread. If you mean the latter, then it AFAIU would need
a serious redesign of the Emacs event queue, to make it accessible
from several threads running in parallel at once.
> > Again, I don't see the wider picture. Are you familiar with how the
> > current JIT font-lock works? If so, can you explain which parts of
> > that will be replaced/modified, and how?
>
> AFAIK the initial tree-sitter parsing (which does not involve anything
> emacs related) may take 200-300ms. In other editors (e.g. vscode) this
> part is not happening on the UI thread but in some extenal background
> thread which then passes the AST to the main UI thread to do the actual
> fontlock. IMO this model might be replicated in emacs in the event of TS
> integration.
What you describe is very different from how JIT font-lock works now.
Which is why I asked the question: I know (more or less) how it works
in other editors, I just don't yet understand well enough how
something like that would fit into the existing fontification
framework. I hope there is a way of fitting it, because otherwise it
would mean a serious surgery of the display engine as well, which will
make the job significantly larger and harder.
next prev parent reply other threads:[~2020-06-24 18:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 7:14 bug#42028: [Feature Request] 27.0.91; Provide the ability dynamic modules to post events in emacs event loop Ivan Yonchovski
2020-06-24 14:44 ` Eli Zaretskii
2020-06-24 16:17 ` yyoncho
2020-06-24 16:28 ` Eli Zaretskii
2020-06-24 16:46 ` yyoncho
2020-06-24 17:07 ` Eli Zaretskii
2020-06-24 17:33 ` Ivan Yonchovski
2020-06-24 18:04 ` Eli Zaretskii [this message]
2020-06-24 18:38 ` Ivan Yonchovski
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=83y2ocs5kr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=42028@debbugs.gnu.org \
--cc=yyoncho@gmail.com \
/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).