From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#55451: 28.1.50; Executing (jit-lock-mode -1) does not disable jit-lock-mode Date: Thu, 19 May 2022 17:00:36 +0300 Message-ID: <83mtfdd3ln.fsf@gnu.org> References: <871qwtshk5.fsf@localhost> <83sfp9iie5.fsf@gnu.org> <87bkvwjatb.fsf@gnus.org> <871qwr2hd0.fsf@localhost> <87zgjeagyp.fsf@gnus.org> <83ilq2eo26.fsf@gnu.org> <87czg94opq.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12581"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, 55451@debbugs.gnu.org To: Ihor Radchenko Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu May 19 16:10:22 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nrgr7-00036Z-F1 for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 19 May 2022 16:10:21 +0200 Original-Received: from localhost ([::1]:55786 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nrgr6-0000K7-8U for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 19 May 2022 10:10:20 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41504) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nrgiD-0003Ep-LV for bug-gnu-emacs@gnu.org; Thu, 19 May 2022 10:01:09 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:42422) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nrgi6-00023x-60 for bug-gnu-emacs@gnu.org; Thu, 19 May 2022 10:01:07 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nrgi6-0002E6-4O for bug-gnu-emacs@gnu.org; Thu, 19 May 2022 10:01:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 19 May 2022 14:01:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 55451 X-GNU-PR-Package: emacs Original-Received: via spool by 55451-submit@debbugs.gnu.org id=B55451.16529688488530 (code B ref 55451); Thu, 19 May 2022 14:01:02 +0000 Original-Received: (at 55451) by debbugs.gnu.org; 19 May 2022 14:00:48 +0000 Original-Received: from localhost ([127.0.0.1]:36319 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nrghr-0002DW-SY for submit@debbugs.gnu.org; Thu, 19 May 2022 10:00:48 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:48102) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nrghq-0002DK-9U for 55451@debbugs.gnu.org; Thu, 19 May 2022 10:00:46 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:57098) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nrghk-000226-Sm; Thu, 19 May 2022 10:00:40 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=PwD5Z7lKJJsW8QQf/US/gvzZsGXfBhGwKSXCuYRunRw=; b=YlnDFASBY6w0 IoP7NB99vCf7+546Y+Ukra277QpSpqZlOKT3WRKEdsTXKcdTLtxx2KFE9n0QTehU3C+j0iQZiiZ7Y /D7W+E7TwSfN9Bt7sJGGEqlIZ20f5nvtaoKJ8B7URgyDxukdWHbr5Aqhe8H5c5JFCClnF9sivrf5t 7gibtDQmNBEIfQHmTvjDrgiL+ikP7Ultsa/MWlBjcnw8jsNHD+fHgnwJkQlutIb/RegFgS/wb+g65 4XkQsVoEZ4ipBg31NyyjuJN/DMvy1dqr37sZzKY9vGvKd4m9H+KjP2MNRpDcFd4EJ1kC+iPPMJt9I ab0ORfLMKrbkDH3LObdmTQ==; Original-Received: from [87.69.77.57] (port=1472 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nrghj-0000k3-Bn; Thu, 19 May 2022 10:00:40 -0400 In-Reply-To: <87czg94opq.fsf@localhost> (message from Ihor Radchenko on Thu, 19 May 2022 21:49:21 +0800) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:232649 Archived-At: > From: Ihor Radchenko > Cc: Lars Ingebrigtsen , 55451@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.