From: Holger Schurig <holgerschurig@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>, Ergus <spacibba@aol.com>
Cc: Emacs-devel@gnu.org
Subject: Re: tree-sitter: conceptional problem solvable at Emacs' level?
Date: Fri, 10 Feb 2023 07:41:57 +0000 [thread overview]
Message-ID: <CAOpc7mE7wZvaPP4cmwNrSsQ35bUg3v5LxU=vGjGeZvTK3Kp-5A@mail.gmail.com> (raw)
In-Reply-To: <06865b3b-9998-8152-1a53-691f0fa0651f@yandex.ru>
> https://github.com/tree-sitter/tree-sitter-cpp/issues/85
From January 2021
Inconclusive.
> https://github.com/tree-sitter/tree-sitter-cpp/issues/40
From June 2019
Speaks about regenerating the parser based on environment variabled.
That means you'll have to have the whole NPM toolchain installed.
Final suggestion is replacing things with spaces before feeding the data to
tree-sitter. That would keep offsets intact.
> https://github.com/tree-sitter/tree-sitter-cpp/issues/146
From January 2022
Points to alternate parsers for C++ dialects, here for OpenFOAM code.
Given that these bugs are sitting there for sometimes years, I can
conclude that the tree-sitter project doesn't care at all. Or lacks
the manpower. Or assigns it differently. Or that the core developers of
it have different itches to scratch.
Whatever the reason, I wouldn't hold my breath that anything changes on
their side soon.
The last idea from their bug 40 sounds like it could be implemented on
Emacs side.
prev parent reply other threads:[~2023-02-10 7:41 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
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 [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOpc7mE7wZvaPP4cmwNrSsQ35bUg3v5LxU=vGjGeZvTK3Kp-5A@mail.gmail.com' \
--to=holgerschurig@gmail.com \
--cc=Emacs-devel@gnu.org \
--cc=dgutov@yandex.ru \
--cc=spacibba@aol.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.