unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Filippo Argiolas <filippo.argiolas@gmail.com>
Cc: spacibba@aol.com, emacs-devel@gnu.org, casouri@gmail.com
Subject: Re: A few questions about c++-ts-mode.
Date: Thu, 09 May 2024 08:53:01 +0300	[thread overview]
Message-ID: <86cypv8rb6.fsf@gnu.org> (raw)
In-Reply-To: <CAOdrLGKJpGc57YAQy=D_sn6W_Hbc6f1co+hrsZuRH1+xSVfOkg@mail.gmail.com> (message from Filippo Argiolas on Thu, 9 May 2024 07:34:58 +0200)

> From: Filippo Argiolas <filippo.argiolas@gmail.com>
> Date: Thu, 9 May 2024 07:34:58 +0200
> Cc: Ergus <spacibba@aol.com>, emacs-devel@gnu.org, casouri@gmail.com
> 
> > If the only solution is language injection, then doing that our usual
> > way (with regexps etc.) is easier and more flexible.  I thought I saw
> > some commits in the C++ grammar that actually support that in the
> > grammar itself.  If there is such support, we should use it, IMO.
> >
> 
> Sorry to intrude, may I ask what's the problem with language
> injection? it seems the perfect use case for this.

I didn't say there was a problem, I said that doing it with regexp
etc. would be easier and more flexible.

Language injection AFAIU requires an additional grammar library, which
means someone must compile it, the end-user must ensure it's
installed, etc.  IOW, it makes the disadvantages of tree-sitter more
prominent, for the benefit of a very minor feature.  From where I
stand, that makes the balance tip in favor of the simpler solution,
which users could more easily activate and customize.



  reply	other threads:[~2024-05-09  5:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fakigaygsqcunvvbm2zscn7qlkxi234f574ul3hl5vrhymm22k.ref@syjmsievkpp3>
2024-05-07 22:59 ` A few questions about c++-ts-mode Ergus
2024-05-08  0:19   ` Yuan Fu
2024-05-08  1:26     ` Ergus
2024-05-09  4:29       ` Yuan Fu
2024-05-09  6:18         ` Filippo Argiolas
2024-05-12 20:11         ` Ergus
2024-05-08 13:35     ` Eli Zaretskii
2024-05-08 21:05       ` Ergus
2024-05-09  0:16         ` Yuan Fu
2024-05-09  5:17           ` Eli Zaretskii
2024-05-09  5:03         ` Eli Zaretskii
2024-05-09  5:34           ` Filippo Argiolas
2024-05-09  5:53             ` Eli Zaretskii [this message]
2024-05-09  6:11               ` Filippo Argiolas
2024-05-09  7:03                 ` Eli Zaretskii
2024-05-13  6:23               ` Filippo Argiolas
2024-05-13  8:10                 ` Filippo Argiolas

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=86cypv8rb6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=casouri@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=filippo.argiolas@gmail.com \
    --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 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).