GNU bug report logs - #70465
[PATCH] Add font-locking rule for Rust function signatures

Previous Next

Full log

View this message in rfc822 format

From: Noah Peart <noah.v.peart <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Yuan Fu <casouri <at> gmail.com>, 70465 <at> debbugs.gnu.org
Subject: bug#70465: [PATCH] Add font-locking rule for Rust function signatures
Date: Fri, 19 Apr 2024 09:47:38 -0700

[Message part 1 (text/plain, inline)]

> Please be sure to add the bug number to the commit log message when
you install this.

When submitting a patch, is there an easy way to add the bug number to
the commit?

On Fri, Apr 19, 2024 at 3:47 AM Eli Zaretskii <eliz <at> gnu.org> wrote:

> > Cc: 70465 <at> debbugs.gnu.org
> > From: Yuan Fu <casouri <at> gmail.com>
> > Date: Fri, 19 Apr 2024 00:24:49 -0700
> >
> >
> > Noah Peart <noah.v.peart <at> gmail.com> writes:
> >
> > > Tags: patch
> > >
> > > Adds a rule to font-lock Rust function signatures and missing function
> > > modifier "default" to rust-ts-mode--keywords.
> > >
> > > The new rule adds font-locking to signatures as in the following
> > > example:
> > >
> > >     trait Foo {
> > >         fn foo() -> String;
> > > //            ^ font-lock-function-name-face
> > >     }
> >
> > Thanks!
> >
> > Eli, for this kind of small fix patches, should it go to emacs-29 or
> > master? I don’t think it’ll affect the stability of emacs-29, but in the
> > same time it isn’t an urgent bug either.
>
> Since this is an enhancement, not a bugfix, it should go to master.
>
> Please be sure to add the bug number to the commit log message when
> you install this.
>
> Thanks.
>

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.