all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Trevor Arjeski <tmarjeski@gmail.com>
To: Randy Taylor <dev@rjt.dev>
Cc: Yuan Fu <casouri@gmail.com>, Eli Zaretskii <eliz@gnu.org>,
	74277@debbugs.gnu.org, acidbong@tilde.club
Subject: bug#74277: 29.4; rust-ts-mode doesn't highlight some function calls
Date: Tue, 19 Nov 2024 23:48:24 +0300	[thread overview]
Message-ID: <87r077kl0n.fsf@gmail.com> (raw)
In-Reply-To: <Vem53nlAK50PRLCDHMUPai_iN251-gftbL39juX8-n8NyIAf9FuvU1mqonslSXVNB-4-_u8lTmyZ2Y1UOFLGhGV-Tqjqtu33T8crPxsDZ9g=@rjt.dev> (Randy Taylor's message of "Sun, 10 Nov 2024 21:10:35 +0000")

Randy Taylor <dev@rjt.dev> writes:

Hi all, randomly started looking into this...

> This was discussed briefly awhile back, but it's basically going to
> require special handling because macro invocations don't give us the
> usual dead simple way of doing it.

Is this due to lack of support for injections.scm in Emacs' treesitter
implementation?
http://tree-sitter.github.io/tree-sitter/syntax-highlighting#language-injection

Can't seem to find any traces of that in the current source.

From inspecting this line of code in Neovim, it appears that the
injection on macro_invocation is what forces parsing the macro params as
another source_file.







  reply	other threads:[~2024-11-19 20:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08 20:24 bug#74277: 29.4; rust-ts-mode doesn't highlight some function calls acidbong--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-09  8:52 ` Eli Zaretskii
2024-11-10 21:10   ` Randy Taylor
2024-11-19 20:48     ` Trevor Arjeski [this message]
2024-11-20 12:34       ` Acid Bong via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-20 18:22       ` Trevor Arjeski
2024-11-22  3:30         ` Randy Taylor
2024-11-24  5:18           ` Yuan Fu
2024-11-24  7:17             ` Trevor Arjeski
2024-11-25  7:34               ` Yuan Fu
2024-12-14 19:25             ` Randy Taylor

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=87r077kl0n.fsf@gmail.com \
    --to=tmarjeski@gmail.com \
    --cc=74277@debbugs.gnu.org \
    --cc=acidbong@tilde.club \
    --cc=casouri@gmail.com \
    --cc=dev@rjt.dev \
    --cc=eliz@gnu.org \
    /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.