From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: casouri@gmail.com, luangruo@yahoo.com, holgerschurig@gmail.com,
Emacs-devel@gnu.org
Subject: Re: tree-sitter: conceptional problem solvable at Emacs' level?
Date: Sat, 11 Feb 2023 12:42:10 +0200 [thread overview]
Message-ID: <83cz6gjxfh.fsf@gnu.org> (raw)
In-Reply-To: <87bkm0czpp.fsf@localhost> (message from Ihor Radchenko on Sat, 11 Feb 2023 09:34:42 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: Yuan Fu <casouri@gmail.com>, luangruo@yahoo.com,
> holgerschurig@gmail.com, Emacs-devel@gnu.org
> Date: Sat, 11 Feb 2023 09:34:42 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Another possibility is to complicate the function we pass to
> > tree-sitter with which to read buffer text, in a way that replaces the
> > text of a macro with something else (in the simplest case, just space
> > characters), so as to avoid errors in the parser, and again analyze
> > the macros in our own code.
>
> Another idea is delegating parts of buffer to Elisp/alternative parser.
Could be. However:
> Tree sitter provides support to documents written using a mixture of
> grammars: https://tree-sitter.github.io/tree-sitter/using-parsers#multi-language-documents
> Macros can be considered such a "mixed" grammar with macros being a
> grammar of their own.
>
> AFAIU, tree sitter allows excluding certain file ranges from parsing
> and instead parse the excluded ranges using alternative grammar. If
> Elisp can somehow tell tree-sitter backend not skip parsing
> macro-looking lines, it should solve the problem at least partially.
I believe the problem is with handling the parts which _use_ the
macro, not those parts which _define_ macros.
Still, this idea should be explored, I think.
Thanks.
next prev parent reply other threads:[~2023-02-11 10:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 8:09 tree-sitter: conceptional problem solvable at Emacs' level? Holger Schurig
2023-02-09 8:17 ` Po Lu
2023-02-09 8:50 ` Eli Zaretskii
2023-02-09 10:13 ` Po Lu
2023-02-09 10:55 ` Eli Zaretskii
2023-02-10 7:33 ` Yuan Fu
2023-02-10 8:42 ` Eli Zaretskii
[not found] ` <CAOpc7mHX6s0B8vdDee+9FMvQejGTSL3jzgwVekS7Esg-AOf=jw@mail.gmail.com>
2023-02-10 11:48 ` Eli Zaretskii
2023-02-11 2:17 ` Po Lu
2023-02-11 6:25 ` Konstantin Kharlamov
2023-02-11 6:36 ` Konstantin Kharlamov
2023-02-11 6:51 ` Theodor Thornhill
2023-02-11 7:11 ` Konstantin Kharlamov
2023-02-11 7:53 ` Konstantin Kharlamov
2023-02-11 8:22 ` Konstantin Kharlamov
2023-02-11 8:41 ` Theodor Thornhill
2023-02-11 9:37 ` Konstantin Kharlamov
2023-02-11 10:25 ` Konstantin Kharlamov
2023-02-11 8:43 ` Eli Zaretskii
2023-04-16 19:21 ` Konstantin Kharlamov
2023-02-11 9:34 ` Ihor Radchenko
2023-02-11 10:42 ` Eli Zaretskii [this message]
2023-02-11 13:58 ` Lynn Winebarger
2023-02-09 16:25 ` Ergus
2023-02-09 20:09 ` Dmitry Gutov
2023-02-10 7:41 ` Holger Schurig
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=83cz6gjxfh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Emacs-devel@gnu.org \
--cc=casouri@gmail.com \
--cc=holgerschurig@gmail.com \
--cc=luangruo@yahoo.com \
--cc=yantar92@posteo.net \
/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.