From: Yuan Fu <casouri@gmail.com>
To: "Daniel Martín" <mardani29@yahoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: Simplify the tree-sitter parser creation API
Date: Thu, 16 Jun 2022 12:21:35 -0700 [thread overview]
Message-ID: <D9296D4E-7DC1-4C54-AE6C-B8AEE707AF94@gmail.com> (raw)
In-Reply-To: <CBAFADC7-174E-40DC-A26A-175CC7A84C99@gmail.com>
>
> Thanks! I think it makes sense. Though I’d keep the treesit-parser-create function because it directly corresponds to the tree-sitter C API. I can extend the C definition of treesit-parser-create to
>
> (treesit-parser-create LANGUAGE &optional BUFFER NO-REUSE)
>
And done. Please also see the “main” thread for other changes ;-)
Yuan
prev parent reply other threads:[~2022-06-16 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m1pmke7tcn.fsf.ref@yahoo.es>
2022-05-15 14:39 ` Simplify the tree-sitter parser creation API Daniel Martín
2022-05-16 20:50 ` Yuan Fu
2022-06-16 19:21 ` Yuan Fu [this message]
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=D9296D4E-7DC1-4C54-AE6C-B8AEE707AF94@gmail.com \
--to=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mardani29@yahoo.es \
/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).