From: arthur miller <arthur.miller@live.com>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "alan@idiocy.org" <alan@idiocy.org>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: Using incremental parsing in Emacs
Date: Sun, 5 Jan 2020 19:23:16 +0000 [thread overview]
Message-ID: <VI1P194MB0429C500AC68B5A51575B37C963D0@VI1P194MB0429.EURP194.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <83eewdg3vy.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]
I think there are two use-cases:
1) batch processing where entire file (or visible portion) is processed by different thread(s), for example on file opening or if some expansion takes place (yasnippet or similar).
This can be done by dividing text in number of blocks (lines or similar) and letting each thread match block atva time against shared pattern database.
2) interactive use; when user is typing actively.
Interactive use is easy, just match ladt word after certain delimiters are typed. Probably does not need threading, but can't be done with multiple threads as well. Multiple threads can match one word at a time against patterns database split in blocks. Case 2 is probably not worth the round-trip time to the bus, but I don't know.
Just as a thought. Would it be possible?
Skickat från min Samsung Galaxy-smartphone.
-------- Originalmeddelande --------
Från: Eli Zaretskii <eliz@gnu.org>
Datum: 2020-01-05 19:22 (GMT+01:00)
Till: Stefan Monnier <monnier@iro.umontreal.ca>
Kopia: alan@idiocy.org, emacs-devel@gnu.org
Ämne: Re: Using incremental parsing in Emacs
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> Date: Sun, 05 Jan 2020 12:09:08 -0500
>
> I was more thinking about having the new system work concurrently
> with the rest of Elisp. I.e. have one CPU run Elisp while other
> CPU(s) do the syntax processing,
How do you give the syntax-processing thread access to buffer text, if
it's running asynchronously?
[-- Attachment #2: Type: text/html, Size: 2667 bytes --]
next prev parent reply other threads:[~2020-01-05 19:23 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 10:05 Using incremental parsing in Emacs Eli Zaretskii
2020-01-03 13:36 ` phillip.lord
2020-01-03 14:24 ` Eli Zaretskii
2020-01-03 15:43 ` arthur miller
2020-01-03 16:00 ` Dmitry Gutov
2020-01-03 17:09 ` Pankaj Jangid
2020-01-03 19:39 ` Stephen Leake
2020-01-03 20:05 ` Eli Zaretskii
2020-01-03 22:21 ` arthur miller
2020-01-04 3:46 ` HaiJun Zhang
2020-01-04 8:23 ` Eli Zaretskii
2020-01-03 23:53 ` Stephen Leake
2020-01-04 8:45 ` Eli Zaretskii
2020-01-04 14:05 ` arthur miller
2020-01-04 19:26 ` Stephen Leake
2020-01-04 19:54 ` Eli Zaretskii
2020-01-05 17:05 ` Stephen Leake
2020-01-05 19:14 ` yyoncho
2020-01-05 22:44 ` Dmitry Gutov
2020-01-04 3:59 ` HaiJun Zhang
[not found] ` <41b3e9a0-2866-4692-a35c-6d9541bc3aaa@Spark>
2020-01-04 4:57 ` HaiJun Zhang
2020-01-04 8:55 ` Eli Zaretskii
2020-01-04 12:50 ` VanL
2020-01-04 13:22 ` arthur miller
2020-01-04 23:47 ` Replacing all C code???? Richard Stallman
2020-01-05 3:35 ` VanL
2020-01-05 22:19 ` Richard Stallman
2020-01-05 5:01 ` Stefan Monnier
2020-01-05 16:58 ` Fangrui Song
2020-01-05 22:18 ` Richard Stallman
2020-01-05 22:25 ` Stefan Monnier
2020-01-07 2:34 ` VanL
2020-01-04 13:30 ` Using incremental parsing in Emacs arthur miller
2020-01-04 13:42 ` Dmitry Gutov
2020-01-04 14:46 ` arthur miller
2020-01-05 14:50 ` Alan Third
2020-01-05 15:16 ` arthur miller
2020-01-05 15:29 ` Eli Zaretskii
2020-01-05 15:31 ` Eli Zaretskii
2020-01-05 17:11 ` Stephen Leake
2020-01-09 21:56 ` Dmitry Gutov
2020-01-10 7:41 ` Eli Zaretskii
2020-01-11 1:41 ` Dmitry Gutov
2020-01-11 7:53 ` Eli Zaretskii
2020-01-11 12:24 ` Dmitry Gutov
2020-01-11 12:29 ` Eli Zaretskii
2020-01-04 20:26 ` Yuan Fu
2020-01-04 20:43 ` Stefan Monnier
2020-01-05 14:19 ` Alan Third
2020-01-05 17:07 ` Stephen Leake
2020-01-05 19:16 ` Alan Third
2020-01-05 17:09 ` Stefan Monnier
2020-01-05 18:22 ` Eli Zaretskii
2020-01-05 19:18 ` Stefan Monnier
2020-01-05 19:36 ` Eli Zaretskii
2020-01-05 20:27 ` Stefan Monnier
2020-01-05 21:12 ` yyoncho
2020-01-05 22:10 ` Stefan Monnier
2020-01-05 23:08 ` yyoncho
2020-01-06 3:39 ` Eli Zaretskii
2020-01-05 19:23 ` arthur miller [this message]
2020-01-05 19:40 ` Eli Zaretskii
2020-01-05 20:28 ` arthur miller
2020-01-06 3:42 ` Eli Zaretskii
2020-01-06 4:39 ` HaiJun Zhang
2020-01-06 5:33 ` Eli Zaretskii
2020-01-06 5:55 ` HaiJun Zhang
2020-01-06 6:11 ` Eli Zaretskii
2020-01-06 16:45 ` arthur miller
2020-01-07 16:19 ` Eli Zaretskii
2020-01-06 13:47 ` Stefan Monnier
2020-01-06 16:36 ` HaiJun Zhang
2020-01-06 16:48 ` arthur miller
2020-01-06 16:14 ` Anand Tamariya
[not found] <1504933445.581219.1569619792280.ref@mail.yahoo.com>
2019-09-27 21:29 ` Where to place third-party C source code? Jorge Araya Navarro
2019-09-28 6:31 ` Eli Zaretskii
2019-09-28 7:33 ` Jorge Javier Araya Navarro
2019-09-28 12:54 ` Stefan Monnier
2019-12-26 16:52 ` yyoncho
2020-01-04 3:25 ` Using incremental parsing in Emacs HaiJun Zhang
2020-01-04 5:21 ` Tobias Bading
2020-01-04 23:48 ` Richard Stallman
2020-01-05 3:36 ` Eli Zaretskii
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=VI1P194MB0429C500AC68B5A51575B37C963D0@VI1P194MB0429.EURP194.PROD.OUTLOOK.COM \
--to=arthur.miller@live.com \
--cc=alan@idiocy.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).