From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, yantar92@gmail.com, 55451@debbugs.gnu.org
Subject: bug#55451: 28.1.50; Executing (jit-lock-mode -1) does not disable jit-lock-mode
Date: Thu, 19 May 2022 19:13:43 -0400 [thread overview]
Message-ID: <E1nrpKx-00056q-An@fencepost.gnu.org> (raw)
In-Reply-To: <83ilq2eo26.fsf@gnu.org> (message from Eli Zaretskii on Wed, 18 May 2022 20:41:05 +0300)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> 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.
I don't think I have ever turned off Jit-Lock mode _as such_, but I
turn off Font-Lock mode in some major modes. I don't know whether
that is that pertinent to this issue; I mention it just in case.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2022-05-19 23:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 14:00 bug#55451: 28.1.50; Executing (jit-lock-mode -1) does not disable jit-lock-mode Ihor Radchenko
2022-05-16 15:53 ` Eli Zaretskii
2022-05-17 18:03 ` Lars Ingebrigtsen
2022-05-18 11:46 ` Ihor Radchenko
2022-05-18 17:27 ` Lars Ingebrigtsen
2022-05-18 17:41 ` Eli Zaretskii
2022-05-19 13:49 ` Ihor Radchenko
2022-05-19 14:00 ` Eli Zaretskii
2022-05-20 8:13 ` Ihor Radchenko
2022-05-19 23:13 ` Richard Stallman [this message]
2022-05-20 6:55 ` Eli Zaretskii
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=E1nrpKx-00056q-An@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=55451@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=yantar92@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 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).