From: Eli Zaretskii <eliz@gnu.org>
To: yyoncho <yyoncho@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Running process filters in another thread
Date: Sat, 29 Sep 2018 00:14:34 +0300 [thread overview]
Message-ID: <83bm8h729x.fsf@gnu.org> (raw)
In-Reply-To: <CACCVLQUQZiURXLow30V4xC_WtTba66PAwEJ0q8Sczxo+qXTG-w@mail.gmail.com> (message from yyoncho on Fri, 28 Sep 2018 21:21:23 +0300)
> From: yyoncho <yyoncho@gmail.com>
> Date: Fri, 28 Sep 2018 21:21:23 +0300
>
> I want to raise this topic regarding the rise of Language servers and the performance
> problems that are related to parsing process output on UI thread.
>
> I am not familiar with emacs internals and I am not sure whether this is doable
> but I wonder whether providing the option to do the parsing(and probably more?)
> in a separate thread and then call the *filter* function on emacs side in UI
> thread with elisp data structures like lists, hashmaps etc. instead of raw
> string is feasible which would be similar to what is happening in Javascript world.
Emacs threads are cooperative, and only one thread can run at any
given time. So it i's unclear to me how running process filters in a
separate thread will help improve the performance in this case,
because Emacs will still be locked up when that other thread runs the
filter.
Or am I missing something?
next prev parent reply other threads:[~2018-09-28 21:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 18:21 Running process filters in another thread yyoncho
2018-09-28 21:14 ` Eli Zaretskii [this message]
[not found] ` <CACCVLQUrpxuhKwaHbFfCSzYLfucL8x+tJOkwgKwK8bzb0VZaWg@mail.gmail.com>
2018-09-29 6:54 ` Fwd: " yyoncho
2018-09-29 7:37 ` Eli Zaretskii
2018-09-28 23:03 ` Stefan Monnier
2018-09-29 7:35 ` yyoncho
2018-09-29 8:15 ` Eli Zaretskii
2018-09-29 18:10 ` Stefan Monnier
2018-09-29 19:23 ` yyoncho
2018-09-29 20:30 ` Stefan Monnier
2018-09-30 7:08 ` yyoncho
2018-09-30 13:01 ` Stefan Monnier
2018-09-30 15:01 ` yyoncho
2018-10-01 21:12 ` Tom Tromey
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=83bm8h729x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@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).