From: Randy Taylor <dev@rjt.dev>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acidbong@tilde.club, 74277@debbugs.gnu.org, Yuan Fu <casouri@gmail.com>
Subject: bug#74277: 29.4; rust-ts-mode doesn't highlight some function calls
Date: Sun, 10 Nov 2024 21:10:35 +0000 [thread overview]
Message-ID: <Vem53nlAK50PRLCDHMUPai_iN251-gftbL39juX8-n8NyIAf9FuvU1mqonslSXVNB-4-_u8lTmyZ2Y1UOFLGhGV-Tqjqtu33T8crPxsDZ9g=@rjt.dev> (raw)
In-Reply-To: <86bjyookld.fsf@gnu.org>
On Saturday, November 9th, 2024 at 03:52, Eli Zaretskii <eliz@gnu.org> wrote:
>
>
> > Date: Fri, 08 Nov 2024 20:24:07 +0000
>
> > From: acidbong--- via "Bug reports for GNU Emacs,
> > the Swiss army knife of text editors" bug-gnu-emacs@gnu.org
> >
> > rust-ts-mode highlights function calls when they're used in an
> > assignment or as statements, but not in string formatting:
> >
> > `println!("Some line and {}", some_function(a, b)) # ^^^^^^^^^^^^^ this is not getting highlighted`
> >
> > This is how it looks in Emacs (treesit-level is 4 btw):
> > https://matrix.envs.net/_matrix/media/r0/download/envs.net/66652827fc7545e57d2eef263ee28ef6bc2ef1c01854976160883015680
> >
> > This is how it looks in Neovim (with treesitter highlighting on):
> > https://matrix.envs.net/_matrix/media/r0/download/envs.net/382a104ee3e6e4dacabebfa7f84f4b9b7231b1171854976151936565248
> >
> > -----------------------------------
>
>
> Thanks.
>
> Randy/Yuan, any suggestions or fixes?
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.
Maybe it's easy enough to see if the identifier has parentheses
immediately following it...
I probably won't have a chance to take a crack at it anytime soon, so
if anyone wants to beat me to it, feel free.
prev parent reply other threads:[~2024-11-10 21:10 UTC|newest]
Thread overview: 3+ 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 [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
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='Vem53nlAK50PRLCDHMUPai_iN251-gftbL39juX8-n8NyIAf9FuvU1mqonslSXVNB-4-_u8lTmyZ2Y1UOFLGhGV-Tqjqtu33T8crPxsDZ9g=@rjt.dev' \
--to=dev@rjt.dev \
--cc=74277@debbugs.gnu.org \
--cc=acidbong@tilde.club \
--cc=casouri@gmail.com \
--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 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).