[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
master 514cfbb267: Explain more about jit-lock-mode calling conventions
From: |
Lars Ingebrigtsen |
Subject: |
master 514cfbb267: Explain more about jit-lock-mode calling conventions |
Date: |
Tue, 17 May 2022 14:04:07 -0400 (EDT) |
branch: master
commit 514cfbb267ee678f5b2d6aa6c9824fb32b3ac69d
Author: Lars Ingebrigtsen <larsi@gnus.org>
Commit: Lars Ingebrigtsen <larsi@gnus.org>
Explain more about jit-lock-mode calling conventions
* lisp/jit-lock.el (jit-lock-mode): Explicitly explain ARG
(bug#55451).
---
lisp/jit-lock.el | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/lisp/jit-lock.el b/lisp/jit-lock.el
index 20c1202474..17969d5762 100644
--- a/lisp/jit-lock.el
+++ b/lisp/jit-lock.el
@@ -217,6 +217,11 @@ If the system load rises above `jit-lock-stealth-load'
percent, stealth
fontification is suspended. Stealth fontification intensity is controlled via
the variable `jit-lock-stealth-nice'.
+`jit-lock-mode' is not a regular minor mode, and it doesn't
+follow the regular conventions to switch the functionality on or
+off. Instead, an ARG of nil will switch it off, and non-nil will
+switch it on.
+
If you need to debug code run from jit-lock, see `jit-lock-debug-mode'."
(setq jit-lock-mode arg)
(cond
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- master 514cfbb267: Explain more about jit-lock-mode calling conventions,
Lars Ingebrigtsen <=