From: Yuan Fu <casouri@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Huan Nguyen <nguyenthieuhuan@gmail.com>, emacs-devel@gnu.org
Subject: Re: [PATCH] treesit.el: New function to describe font-lock rules
Date: Sat, 21 Oct 2023 12:49:44 -0700 [thread overview]
Message-ID: <D2052BC6-FC42-4A43-934A-6FC28CE87114@gmail.com> (raw)
In-Reply-To: <C51951D5-6E55-432F-94FC-603433BD4DEB@gmail.com>
> On Oct 21, 2023, at 1:17 AM, Yuan Fu <casouri@gmail.com> wrote:
>
>
>
>> On Oct 21, 2023, at 12:38 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>>
>>> From: Yuan Fu <casouri@gmail.com>
>>> Date: Fri, 20 Oct 2023 21:11:01 -0700
>>> Cc: emacs-devel <emacs-devel@gnu.org>,
>>> Eli Zaretskii <eliz@gnu.org>
>>>
>>> Great! I’ve pushed it to master. Eli, do we need a NEWS entry for this change? We are adding a new keyword for treesit-font-lock-rules. I attached the merged patch below.
>>
>> Not only a NEWS entry is in order, we should also document this
>> keyword in the ELisp manual, where the other keywords of
>> treesit-font-lock-rules are documented.
>>
>> Thanks.
>
> Yes, absolutely.
>
> Yuan
Done.
Yuan
prev parent reply other threads:[~2023-10-21 19:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 13:32 [PATCH] treesit.el: New function to describe font-lock rules Huan Thieu Nguyen
2023-10-06 7:05 ` Yuan Fu
[not found] ` <1e5cd9da-7be2-486d-bbbb-7b50167e2916@gmail.com>
[not found] ` <35F71E15-AEAB-45FD-ACF3-50133A1766D8@gmail.com>
[not found] ` <2c196077-a1c7-4bfa-91b6-209ebf21b6fa@gmail.com>
[not found] ` <CB77885F-776A-4397-83E6-07835269FE50@gmail.com>
[not found] ` <91640cdb-d78a-4bd5-895c-9aacca3d4c97@gmail.com>
[not found] ` <E07BF33E-BD63-42F1-8B7E-FF110CE9642E@gmail.com>
[not found] ` <CALZcaFhB=oOFcO4arckFCMVbddkPb9xPQRAfUiDZp2_f=qd9fA@mail.gmail.com>
2023-10-21 4:11 ` Yuan Fu
2023-10-21 7:38 ` Eli Zaretskii
2023-10-21 8:17 ` Yuan Fu
2023-10-21 19:49 ` Yuan Fu [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D2052BC6-FC42-4A43-934A-6FC28CE87114@gmail.com \
--to=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nguyenthieuhuan@gmail.com \
/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.