From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: arthur.miller@live.com, emacs-devel@gnu.org
Subject: Re: Using incremental parsing in Emacs
Date: Sat, 11 Jan 2020 09:53:24 +0200 [thread overview]
Message-ID: <83h8128m4r.fsf@gnu.org> (raw)
In-Reply-To: <b8f4dd3c-728f-8de5-fbbc-62fafa834f36@yandex.ru> (message from Dmitry Gutov on Sat, 11 Jan 2020 04:41:53 +0300)
> Cc: arthur.miller@live.com, emacs-devel@gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Sat, 11 Jan 2020 04:41:53 +0300
>
> > If we provide infrastructure for using the likes of Tree-Sitter in
> > core, how long do you think it will take until someone rewrites their
> > JS generator of parse tables in Lisp? And we already have machinery
> > in place for loading external shared objects; it can be extended if
> > necessary to handle loading parse tables.
>
> It's should be easy enough to convert between the JS and Lisp syntax.
> But how do you compile it to a library that Tree-Sitter expects without
> having the user install a C compiler toolchain?
Yes, users who want to compile their own parsers, or recompile
existing ones, will have to have a C compiler installed. Which is a
downside, but not a serious one in this case, IMO, because most users
will use existing parser tables. I'd expect most if not all of such
tables to come together with the Emacs-adapted Tree-Sitter package, or
be available on ELPA, or even (gasp!) in core.
> IIRC you objected against features relying on something like this in the
> past.
If users need to make changes in this stuff frequently, then yes, it's
a serious disadvantage to need a compiler. But it doesn't seem to be
the case here, not up front anyway.
next prev parent reply other threads:[~2020-01-11 7:53 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h8128m4r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arthur.miller@live.com \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.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.