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: Mon, 10 Aug 2020 18:25:54 -0400 Message-ID: References: <83364v5j28.fsf@gnu.org> <83y2mm4n07.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9085"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: stefankangas@gmail.com, jnorden@tntech.edu, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Aug 11 00:26:31 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 1k5GFT-0002Fu-0A for ged-emacs-devel@m.gmane-mx.org; Tue, 11 Aug 2020 00:26:31 +0200 Original-Received: from localhost ([::1]:34500 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k5GFS-0007tg-2M for ged-emacs-devel@m.gmane-mx.org; Mon, 10 Aug 2020 18:26:30 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52096) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k5GEy-0007RH-AS for emacs-devel@gnu.org; Mon, 10 Aug 2020 18:26:00 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:54184) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k5GEw-00065y-DM; Mon, 10 Aug 2020 18:25:59 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id D5DFC1005A8; Mon, 10 Aug 2020 18:25:56 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 606D810035B; Mon, 10 Aug 2020 18:25:55 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1597098355; bh=H9heXkfSWgyFcPoA5p/lTHRRbEUFcK6Z+n7NLH3khI4=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=NfniY7OKMbdqk6f+vF7QJzN37ShQyNo1+z8DgjzBpmtCaaXxOg9jlljTau3vzfsU8 XSp4IAOB55o7/IcGl7cMmiFPxPIyPUBQCINszzSBKs1TC5vQ6UhrpNXL89aTTpFbof OBZ3d+poMU+gqQRJNHbqlyX5V6RzYTCK0gkwX9rZ1gdsmQXB1oKPO+kjO/1Rvu0CWh Om2RPVRZd924k4qQJkzlkOKipx/DOUxkhghbKw9TBafW4Yk/TK1n2tQP0TJa3waYAV BI9/L2Atl+RjGc1FGH8qECNHzVfcwm70t9bI/sba2JJErIsv9G8lfTHUwEbAd7tsfN MhdmNtP4lREFA== Original-Received: from milanesa (unknown [45.72.246.108]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 1485D120784; Mon, 10 Aug 2020 18:25:55 -0400 (EDT) In-Reply-To: <83y2mm4n07.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 10 Aug 2020 17:02:48 +0300") 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/10 18:19:33 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:253606 Archived-At: > OK, but why does that mean we should demote it from being a defcustom? `defcustom` is mostly useful in order to set it globally in your config file. > People who need to debug font-lock are also users, and being unable to > change the value through "M-x set-variable" is an annoyance, at least > for me. `set-variable` works rather poorly here because it has no immediate effect on the current buffer (until you re-enable font-lock). That's why I'm suggesting a `font-lock-debug-mode` instead. > Do you see any harm in keeping it as a defcustom? If we add `font-lock-debug-mode` I don't see any benefit in keeping it. The harm is limited to accumulating cruft. Stefan