bug#71209: [PATCH] Add font-locking for variables in go-ts-mode range clauses

[Stefan Kangas <stefankangas@gmail.com>]

Noah Peart <noah.v.peart@gmail.com> writes:

> Ah yes, sorry to be slow, I can submit a patch for those settings.  I'll take a look today!

Any updates here?  Thanks!

>
> On Thu, Jun 27, 2024 at 3:38 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
>  Ping! Ping!  Noah, are you still interested in working on this?
>
>  > Cc: 71209@debbugs.gnu.org, dev@rjt.dev
>  > Date: Sat, 15 Jun 2024 10:56:36 +0300
>  > From: Eli Zaretskii <eliz@gnu.org>
>  >
>  > Ping!  Noah, would you please answer Dmitry?
>  >
>  > > Cc: 71209@debbugs.gnu.org
>  > > Date: Sat, 1 Jun 2024 17:13:57 +0300
>  > > From: Dmitry Gutov <dmitry@gutov.dev>
>  > >
>  > > On 01/06/2024 04:42, Noah Peart wrote:
>  > > >
>  > > > I've been using these for c++, I think they are still missing
>  > > >
>  > > >      ;; for (auto x: ...)
>  > > >      (for_range_loop
>  > > >       declarator: (identifier) @font-lock-variable-name-face)
>  > > >      ;; auto& x
>  > > >      (reference_declarator
>  > > >       (identifier) @font-lock-variable-name-face)
>  > > >      ;; auto[&] [x, y]
>  > > >      (structured_binding_declarator
>  > > >       _ [(identifier)] @font-lock-variable-name-face)
>  > > >
>  > > > I suppose most people keep the default font-locking for variable-name
>  > > > and variable-use, so these missing rules go unnoticed.
>  > >
>  > > Do you want to submit a full patch with these as well?
>  > >
>  > >
>  > >
>  > >
>  >
>  >
>  >
>  >