From: Yuan Fu <casouri@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
51572@debbugs.gnu.org, dick.r.chiang@gmail.com
Subject: bug#51572: [PATCH] tree-sitter-lock-mode
Date: Fri, 17 Dec 2021 22:26:58 -0800 [thread overview]
Message-ID: <132A4977-20A9-4589-82DE-572663A4594F@gmail.com> (raw)
In-Reply-To: <7BDD6EE1-165A-43B7-9502-CBF3232EB9C2@gmail.com>
>>>
>>> From: Lars Ingebrigtsen <larsi@gnus.org>
>>> Date: Thu, 04 Nov 2021 19:47:16 +0100
>>> Cc: 51572@debbugs.gnu.org
>>>
>>> So I'm not sure where we're going with this. Anybody got an opinion?
>>
>> What's the status of the tree-sitter support that Yuan Fu (CC'ed) was
>> working on? I thought he was very close to completion.
>
> Sorry that I missed this. The code only lacks manual for indentation and font-lock integration. I was waiting for someone to suggest some improvement in that two area before writing the manual but so far no one has provided any. I’ll probably just write the manual and call it done. I’m also waiting for the author of tree-sitter to 1) release 1.0 and 2) allow changing malloc mechanism on run-time.
Someone notified me of this commercial-emacs thing made by dickmao [1]. Looking at his README, I suspect that this report is just an excuse for using the patch on his commercial-emacs. So we can probably close this report. I’m happy to be corrected, of course.
[1] https://github.com/commercial-emacs/commercial-emacs
Yuan
next prev parent reply other threads:[~2021-12-18 6:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 19:03 bug#51572: [PATCH] tree-sitter-lock-mode dick
2021-11-04 18:47 ` Lars Ingebrigtsen
2021-11-04 19:31 ` Eli Zaretskii
2021-11-07 17:21 ` Fu Yuan
2021-12-18 6:26 ` Yuan Fu [this message]
2021-12-18 7:38 ` Eli Zaretskii
2021-12-19 6:56 ` bug#51572: Yuan Fu
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=132A4977-20A9-4589-82DE-572663A4594F@gmail.com \
--to=casouri@gmail.com \
--cc=51572@debbugs.gnu.org \
--cc=dick.r.chiang@gmail.com \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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 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).