From: Eli Zaretskii <eliz@gnu.org>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: master 5c70ff9: New user option 'font-lock-ignore'
Date: Sat, 02 Apr 2022 19:44:24 +0300 [thread overview]
Message-ID: <838rsn4eqf.fsf@gnu.org> (raw)
In-Reply-To: <87zgl3mozw.fsf@gmail.com> (message from Augusto Stoffel on Sat, 02 Apr 2022 18:25:23 +0200)
> From: Augusto Stoffel <arstoffel@gmail.com>
> Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
> Date: Sat, 02 Apr 2022 18:25:23 +0200
>
> On Sat, 2 Apr 2022 at 16:52, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > I made changes to the documentation, please have a look.
>
> Looks good to me. I just have one remark to make:
>
> @@ -3337,23 +3350,23 @@ Line by line, this does the following:
>
> @enumerate
> @item
> -In all programming modes, disable all font-lock keywords that apply
> -one of the standard font-lock faces (excluding strings and comments,
> -which are covered by syntactic Font Lock).
> +In all programming modes, disable fontifications due to all font-lock
> +keywords that apply one of the standard font-lock faces (excluding
> ^^^^^^^^
> Here, we got one stray use of "keyword" in the funny sense of
> font-lock.el
I don't see anything wrong with the new text. What would you use
instead that is more clear?
next prev parent reply other threads:[~2022-04-02 16:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 6:36 master 5c70ff9: New user option 'font-lock-ignore' Eli Zaretskii
2022-04-02 7:34 ` Augusto Stoffel
2022-04-02 10:01 ` Eli Zaretskii
2022-04-02 11:18 ` Augusto Stoffel
2022-04-02 11:58 ` Eli Zaretskii
2022-04-02 12:08 ` Augusto Stoffel
2022-04-02 13:52 ` Eli Zaretskii
2022-04-02 16:25 ` Augusto Stoffel
2022-04-02 16:44 ` Eli Zaretskii [this message]
2022-04-02 16:52 ` Augusto Stoffel
2022-04-02 14:06 ` Stefan Monnier
2022-04-02 15:28 ` [External] : " Drew Adams
2022-04-02 16:25 ` Augusto Stoffel
2022-04-02 18:45 ` Drew Adams
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=838rsn4eqf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arstoffel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).