From: Eli Zaretskii <eliz@gnu.org>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: luangruo@yahoo.com, holgerschurig@gmail.com, Emacs-devel@gnu.org
Subject: Re: tree-sitter: conceptional problem solvable at Emacs' level?
Date: Fri, 10 Feb 2023 13:48:29 +0200 [thread overview]
Message-ID: <83zg9lkagi.fsf@gnu.org> (raw)
In-Reply-To: <CAOpc7mHX6s0B8vdDee+9FMvQejGTSL3jzgwVekS7Esg-AOf=jw@mail.gmail.com> (message from Holger Schurig on Fri, 10 Feb 2023 11:31:39 +0000)
> From: Holger Schurig <holgerschurig@gmail.com>
> Date: Fri, 10 Feb 2023 11:31:39 +0000
>
> > And I'm sure there are other alternatives. This issue is not unique
> > to Emacs, so studying how other IDEs deal with it could also yield
> > ideas.
>
> I'm aware of three FOSS IDEs that are somewhat linked to C++ and/or Qt:
>
> * KDevelop (from the KDE pro project)
> * Kate (dito, although some might not call it an IDE)
> * Qt Creator
>
> For the first two I have no info if they even looked into Tree-Sitter.
>
> However, Qt Creator does't want to implement Tree-Sitter at all, they
> are happy with KSyntaxHighlighting. See
> https://bugreports.qt.io/browse/QTCREATORBUG-26348
>
> KSyntaxHighligting is in turn from the KDE project, and used in KDevelop
> and Kate. So basically all three use the same technology. Which seems to
> work nicely for them.
Thanks.
However, I meant the IDEs which are using tree-sitter and support
developing C/C++ programs. I believe some do.
next prev parent reply other threads:[~2023-02-10 11:48 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 [this message]
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
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=83zg9lkagi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Emacs-devel@gnu.org \
--cc=holgerschurig@gmail.com \
--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 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).