all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: john muhl <jm@pub.pink>
Cc: 67554-done@debbugs.gnu.org
Subject: bug#67554: Acknowledgement ([PATCH] Improve font-lock in lua-ts-mode)
Date: Sat, 02 Dec 2023 15:51:44 +0200	[thread overview]
Message-ID: <83a5qs90gf.fsf@gnu.org> (raw)
In-Reply-To: <877clylpx4.fsf@pub.pink> (bug-gnu-emacs@gnu.org)

> Date: Thu, 30 Nov 2023 18:34:59 -0600
> From:  john muhl via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> 
> >From 5a87b7b231a384c7035e75105bc173fc05f38336 Mon Sep 17 00:00:00 2001
> From: john muhl <jm@pub.pink>
> Date: Tue, 14 Nov 2023 16:25:43 -0600
> Subject: [PATCH] Improve font-locking in lua-ts-mode (bug#67554)
> 
> * lisp/progmodes/lua-ts-mode.el (lua-ts-mode): Move property
> highlighting to level 4.
> (lua-ts--keywords): Remove `true', `false' and `nil' from
> keywords.
> (lua-ts--font-lock-settings): Highlight assignments, functions
> and labels in more places. Distinguish comment delimiters.
> (lua-ts--comment-font-lock): New function.

Thanks, pushed to the master branch (with a couple of minor
adjustments), and closing the bug.





  reply	other threads:[~2023-12-02 13:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30 23:51 bug#67554: [PATCH] Improve font-lock in lua-ts-mode john muhl via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found] ` <handler.67554.B.170138919828765.ack@debbugs.gnu.org>
2023-12-01  0:34   ` bug#67554: Acknowledgement ([PATCH] Improve font-lock in lua-ts-mode) john muhl via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-02 13:51     ` Eli Zaretskii [this message]
2023-12-02 14:08       ` john muhl via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-02 14:51         ` Eli Zaretskii

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=83a5qs90gf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=67554-done@debbugs.gnu.org \
    --cc=jm@pub.pink \
    /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.