all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: yyoncho <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 20:07:50 +0300	[thread overview]
Message-ID: <83zh8ss87t.fsf@gnu.org> (raw)
In-Reply-To: <CACCVLQWXZDzP=RWirouusDcb5pPSw_Mcq9h+hqUVhDsjhrmy0g@mail.gmail.com> (message from yyoncho on Wed, 24 Jun 2020 19:46:56 +0300)

> From: yyoncho <yyoncho@gmail.com>
> Date: Wed, 24 Jun 2020 19:46:56 +0300
> Cc: 42028@debbugs.gnu.org
> 
> 1. JSON parsing to Jansson data structures
> 2. Converting Jasson data structures to lisp data structures.
> 
> If we assume that 1 is taking most of the time

Does it?  Did someone time these separately?

> start(string, callback) -> convert string to char* -> post it to worker thread -> worker thread does the parsing
> -> worker thread post to main loop -> main loop converts Jansson ds to lisp ds -> main loop
> calls the callback passed on start

You cannot easily post to the queue from a worker thread, because the
queue cannot be posted to asynchronously.

And I lack the larger picture: how would this work within a framework
of some Emacs feature?  E.g., how will this processed be triggered,
and by what kind of trigger?

> The same strategy probably could be applied to Font locking with TreeSitter. 

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?





  reply	other threads:[~2020-06-24 17:07 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 [this message]
2020-06-24 17:33           ` Ivan Yonchovski
2020-06-24 18:04             ` Eli Zaretskii
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83zh8ss87t.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 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.