From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Remove obsolete fast-lock and lazy-lock libraries Date: Sun, 09 Aug 2020 15:53:21 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38848"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Eli Zaretskii , stefankangas@gmail.com, emacs-devel@gnu.org To: Jeff Norden Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Aug 09 21:54:06 2020 Return-path: Envelope-to: ged-emacs-devel@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 1k4rOQ-0009zv-2s for ged-emacs-devel@m.gmane-mx.org; Sun, 09 Aug 2020 21:54:06 +0200 Original-Received: from localhost ([::1]:51186 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k4rOP-0001MZ-42 for ged-emacs-devel@m.gmane-mx.org; Sun, 09 Aug 2020 15:54:05 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42162) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k4rNo-0000oU-Au for emacs-devel@gnu.org; Sun, 09 Aug 2020 15:53:28 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:23669) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k4rNm-0004NF-3r; Sun, 09 Aug 2020 15:53:27 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 3E8DC100B1B; Sun, 9 Aug 2020 15:53:24 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id A5F1F1005A8; Sun, 9 Aug 2020 15:53:22 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1597002802; bh=0jG3b1TTCELva1cmvnpMMArFKCy3UH7yJfmqGRSB/vI=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=Q/cOoL/PaMn2d9QjEdHcXK7qjGWMQlawuAvOAjpqq+HSj+0T26LTKFxrBTjgBiQTZ 1UhWXOo82LZJnvkgqWzUit921X/Nl3mts7NAdGFpyuG+NKoDZOk/lLdedm/BaRKqML lJ6ZEqByU05Vjzb3NOEiuIIPhiY3d73lDcDCids05Jbvj9Jb4TubhvAP/A2qXhy98T eLd0JKYILc4bHarlW2OrDgX1/TyDJhdLplofXe5ZQUYXVF2jBvm4jPxX6JgXKpiUZf tkEZxUDQfgRCVHWhnTdx46jOaF8kw7BMNQ5CUrhZmW5vnQ+JmrqBNNoo1ry9CKw/Yy kgoW/01XHIaxg== Original-Received: from milanesa (unknown [45.72.246.108]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 55D5C120268; Sun, 9 Aug 2020 15:53:22 -0400 (EDT) In-Reply-To: (Jeff Norden's message of "Sun, 09 Aug 2020 14:21:55 -0500") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-detected-operating-system: by eggs.gnu.org: First seen = 2020/08/09 15:53:24 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:253560 Archived-At: > I was thinking that a more descriptive name would make it easier for > people to figure out what the variable is for. IMNSHO, that variable should not be a defcustom any more and we shouldn't encourage users to touch it. IOW we should mark it obsolete. We could OTOH add a new command to enter a form of `font-lock-debug-mode` which could disable the use of jit-lock (but not necessarily in exactly the same way as setting `font-lock-support-mode` would, tho it would probably be the most obvious immediate choice in the short term). Stefan