GNU bug report logs -
#55451
28.1.50; Executing (jit-lock-mode -1) does not disable jit-lock-mode
Previous Next
Reported by: Ihor Radchenko <yantar92 <at> gmail.com>
Date: Mon, 16 May 2022 14:01:01 UTC
Severity: normal
Found in version 28.1.50
Fixed in version 29.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
Message #28 received at 55451 <at> debbugs.gnu.org (full text, mbox):
> From: Ihor Radchenko <yantar92 <at> gmail.com>
> Cc: Lars Ingebrigtsen <larsi <at> gnus.org>, 55451 <at> debbugs.gnu.org
> Date: Thu, 19 May 2022 21:49:21 +0800
>
> > Yes. Moreover, it's hardly worth the hassle: who would switch off
> > jit-lock, except for debugging jit-lock? Most people will never do,
> > which is very unlike every minor mode out there -- those are switched
> > on and off all the time. It isn't an accident that we don't have the
> > "M-x jit-lock-mode" command.
>
> That's exactly the situation I had:
> 1. Tried M-x jit-lock-mode. Did not work. Understandable - special minor
> mode.
> 2. M-: (jit-lock-mode -1). No error. Executed.
> 3. Tried to debug something assuming that jit-lock is disabled.
> 4. After several minutes, realised that jit-lock is still working.
But the doc string already caters to your use case:
If you need to debug code run from jit-lock, see `jit-lock-debug-mode'
> I would not expect users to read minor mode docstring every time to
> check if the usual convention is broken.
Users don't need to turn off jit-lock. People who want to debug it,
OTOH, _are_ expected to read the doc string.
This bug report was last modified 3 years and 45 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.