From: Yuan Fu <casouri@gmail.com>
To: Stephen Leake <stephen_leake@stephe-leake.org>
Cc: Andrei Kuznetsov <r12451428287@163.com>,
Eli Zaretskii <eliz@gnu.org>,
manuel@ledu-giraud.fr, emacs-devel@gnu.org
Subject: Re: [SPAM UNSURE] Maybe we're taking a wrong approach towards tree-sitter
Date: Thu, 29 Jul 2021 19:21:39 -0400 [thread overview]
Message-ID: <DDF01B8E-A32C-4FC4-8809-5B6B349E88B7@gmail.com> (raw)
In-Reply-To: <86sfzwogsn.fsf@stephe-leake.org>
> On Jul 29, 2021, at 7:12 PM, Stephen Leake <stephen_leake@stephe-leake.org> wrote:
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Andrei Kuznetsov <r12451428287@163.com>
>>> Date: Wed, 28 Jul 2021 19:48:18 +0800
>>> Cc: Stephen Leake <stephen_leake@stephe-leake.org>, emacs-devel@gnu.org
>>>
>>> Manuel Giraud <manuel@ledu-giraud.fr> writes:
>>>
>>>> I too did not follow the tree-sitter discussion closely. But AFAIU,
>>>> tree-sitter provides tools to generate a parser (in C) from a grammar.
>>>
>>> If that is the case, it certainly seems grave! I don't think an Emacs
>>> that requires source modifications for extending vital editing
>>> functionality is a good idea.
>>
>> TS's code is written in plain C, and doesn't require any regeneration
>> or source modifications. Anything else is misunderstanding.
>
> That's true for the common TS runtime, which implements the parser and
> error recovery, but the code for each language, that builds the LR parse
> table and some other data structures, is generated in C from a grammar
> file written in javascript, and must be linked into Emacs somehow.
Languages don’t need to be linked into Emacs. They can be in dynamic modules.
Yuan
next prev parent reply other threads:[~2021-07-29 23:21 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 1:57 Maybe we're taking a wrong approach towards tree-sitter Andrei Kuznetsov
2021-07-28 3:53 ` [SPAM UNSURE] " Stephen Leake
2021-07-28 8:23 ` Manuel Giraud
2021-07-28 11:48 ` Andrei Kuznetsov
2021-07-28 13:04 ` Eli Zaretskii
2021-07-28 13:14 ` Andrei Kuznetsov
2021-07-28 13:27 ` Eli Zaretskii
2021-07-28 13:31 ` Andrei Kuznetsov
2021-07-28 14:24 ` Dmitry Gutov
2021-07-28 14:36 ` Dmitry Gutov
2021-07-28 14:51 ` Daniele Nicolodi
2021-07-28 16:10 ` Eli Zaretskii
2021-07-28 16:24 ` Perry E. Metzger
2021-07-28 16:29 ` Eli Zaretskii
2021-07-29 23:12 ` Stephen Leake
2021-07-29 23:21 ` Yuan Fu [this message]
2021-07-30 18:38 ` Stephen Leake
2021-07-30 0:41 ` Andrei Kuznetsov
2021-07-30 12:06 ` Arthur Miller
2021-07-30 12:52 ` Óscar Fuentes
2021-07-30 13:30 ` Arthur Miller
2021-07-30 13:57 ` Ergus
2021-07-30 14:52 ` Arthur Miller
2021-07-30 13:59 ` Eli Zaretskii
2021-07-30 15:45 ` Arthur Miller
2021-07-30 13:32 ` Ergus
2021-07-30 15:07 ` Arthur Miller
2021-08-02 22:13 ` Perry E. Metzger
2021-07-30 18:42 ` Stephen Leake
2021-07-30 6:05 ` Eli Zaretskii
2021-07-31 12:12 ` Stephen Leake
2021-07-31 13:07 ` Eli Zaretskii
2021-07-31 16:55 ` Stephen Leake
2021-07-31 17:12 ` Eli Zaretskii
2021-07-28 11:43 ` Andrei Kuznetsov
2021-07-28 11:50 ` Eli Zaretskii
2021-07-28 12:06 ` Andrei Kuznetsov
2021-07-28 13:05 ` Eli Zaretskii
2021-07-28 13:16 ` Andrei Kuznetsov
2021-07-28 12:36 ` Ergus
2021-07-28 13:07 ` Andrei Kuznetsov
2021-07-28 13:16 ` Eli Zaretskii
2021-07-28 13:27 ` Andrei Kuznetsov
2021-07-28 13:32 ` Eli Zaretskii
2021-07-28 13:38 ` Andrei Kuznetsov
2021-07-28 14:41 ` Manuel Giraud
2021-07-28 15:15 ` Perry E. Metzger
2021-07-28 16:10 ` Eli Zaretskii
2021-07-29 23:25 ` [SPAM UNSURE] " Stephen Leake
2021-07-30 0:54 ` Andrei Kuznetsov
2021-07-30 3:02 ` Andrei Kuznetsov
2021-07-30 18:48 ` Stephen Leake
2021-07-28 15:12 ` Perry E. Metzger
2021-07-29 23:28 ` Stephen Leake
2021-07-30 0:19 ` Perry E. Metzger
2021-07-30 18:44 ` [SPAM UNSURE] " Stephen Leake
2021-07-29 4:35 ` Richard Stallman
2021-07-28 15:09 ` Perry E. Metzger
2021-07-29 23:35 ` Stephen Leake
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=DDF01B8E-A32C-4FC4-8809-5B6B349E88B7@gmail.com \
--to=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=manuel@ledu-giraud.fr \
--cc=r12451428287@163.com \
--cc=stephen_leake@stephe-leake.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.