From: Yuan Fu <casouri@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: feature/tree-sitter 88d54756d4 2/2: Check for outdated tree-sitter node when printing
Date: Wed, 2 Nov 2022 20:51:20 -0700 [thread overview]
Message-ID: <405A7004-902F-49A4-9E79-D9F0FC955940@gmail.com> (raw)
In-Reply-To: <878rksg1z1.fsf@yahoo.com>
> On Nov 2, 2022, at 8:18 PM, Po Lu <luangruo@yahoo.com> wrote:
>
> Yuan Fu <casouri@gmail.com> writes:
>
>> +bool treesit_node_uptodate_p (Lisp_Object obj)
>> +{
>> + Lisp_Object lisp_parser = XTS_NODE (obj)->parser;
>> + return XTS_NODE (obj)->timestamp == XTS_PARSER (lisp_parser)->timestamp;
>> +}
>
> This should be:
>
> bool
> treesit_node_uptodate_p (Lisp_Object object)
> {
> ...
>
>> +bool treesit_node_uptodate_p (Lisp_Object obj);
>
> This should read "extern bool treesit_node_uptodate_p (Lisp_Object)".
Cool, thanks. I’ll fix them.
>
> BTW, does the modification to the style patch I asked you to test work?
> You either didn't answer, or it fell into the spam bucket (but I looked
> and found nothing there.)
Ah yes, sorry. I though you are going to change your patch and forgot to follow up. Everything indeed works, except for the following
- return Fmapconcat (intern_c_string ("treesit-pattern-expand"),
- query, build_pure_c_string (" "));
+ return Fmapconcat (Qtreesit_pattern_expand,
Which breaks a test. Why remove the space? Tree-sitter probably can parse it fine without the spaces, but the result is also viewed by users in some cases, where spaces are much appreciated.
Yuan
next prev parent reply other threads:[~2022-11-03 3:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166743655413.25449.4460092570974006982@vcs2.savannah.gnu.org>
[not found] ` <20221103004915.21875C009EC@vcs2.savannah.gnu.org>
2022-11-03 3:18 ` feature/tree-sitter 88d54756d4 2/2: Check for outdated tree-sitter node when printing Po Lu
2022-11-03 3:51 ` Yuan Fu [this message]
2022-11-03 8:09 ` Po Lu
2022-11-03 9:33 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=405A7004-902F-49A4-9E79-D9F0FC955940@gmail.com \
--to=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
/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.