[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
master 2be7599 2/2: Clarify Gnus vs. font locking in the Gnus manual
From: |
Lars Ingebrigtsen |
Subject: |
master 2be7599 2/2: Clarify Gnus vs. font locking in the Gnus manual |
Date: |
Thu, 9 Sep 2021 09:42:08 -0400 (EDT) |
branch: master
commit 2be75990a7ae611e8596a91b5e124dc421ec93b4
Author: Lars Ingebrigtsen <larsi@gnus.org>
Commit: Lars Ingebrigtsen <larsi@gnus.org>
Clarify Gnus vs. font locking in the Gnus manual
* doc/misc/gnus.texi (Formatting Variables): Explicitly mention
that font locking doesn't work in Gnus buffers (bug#50474).
---
doc/misc/gnus.texi | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/doc/misc/gnus.texi b/doc/misc/gnus.texi
index b384764..4559ae8 100644
--- a/doc/misc/gnus.texi
+++ b/doc/misc/gnus.texi
@@ -22727,6 +22727,13 @@ output lines in the various buffers. There's quite a
lot of them.
Fortunately, they all use the same syntax, so there's not that much to
be annoyed by.
+Gnus does not use the font locking machinery used by most modes in
+Emacs, so switching @code{font-lock-mode} on in the Gnus
+group/summary/article buffers usually doesn't do anything
+useful---instead it'll just mess up the faces that Gnus has already
+put in the buffer. (This is also the case for other minor modes that
+use the font locking machinery, like @code{whitespace-mode}.)
+
Here's an example format spec (from the group buffer): @samp{%M%S%5y:
%(%g%)\n}. We see that it is indeed extremely ugly, and that there are
lots of percentages everywhere.