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 00:02:01 -0400 Message-ID: References: <83364v5j28.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="1989"; 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 Mon Aug 10 06:02:57 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 1k4z1V-0000OR-92 for ged-emacs-devel@m.gmane-mx.org; Mon, 10 Aug 2020 06:02:57 +0200 Original-Received: from localhost ([::1]:50478 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k4z1U-0002Is-8d for ged-emacs-devel@m.gmane-mx.org; Mon, 10 Aug 2020 00:02:56 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47448) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k4z0n-0001sc-5I for emacs-devel@gnu.org; Mon, 10 Aug 2020 00:02:13 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:22007) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k4z0k-0003L8-BK; Mon, 10 Aug 2020 00:02:12 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 4BE71100B1B; Mon, 10 Aug 2020 00:02:07 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 95ACC1005A8; Mon, 10 Aug 2020 00:02:05 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1597032125; bh=+AE15ump6lNs1wB7QZiQ6iLXOS7yRw4d4qyjueONxyM=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=ecVAQVXZVUBie87oDkgjruLv5/USf0CcpDt9W8Knb6HHfPFJT7CwAGnbeq7DBnjl3 g2GGK2zAOTrzyawSfJuTZ1wImdPaKWkXEHsxyZQzwjIyLBSJIvRd9LSjtHB5W50Wcc H0RiWKzujfB3WXWwnvZZqa5FwMAtO0PkiKieUOulPfkdHE44tIyICPmZI1Yskk2Ns9 1UUoIbQpLw37oD1ejrv2hvFU/4dpVyPXV5D500WwcSQtiHmdG3wEjWz6+FiXoObcTZ xcGBWQPrgoVqQYlJhCR7st8CMc7x7y27N+WXhZYFD94pwU3oue+Jx4CEfvvaLe8Ed3 lgmitTnC2aw+A== Original-Received: from milanesa (unknown [45.72.246.108]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id AEDA01202C5; Mon, 10 Aug 2020 00:02:04 -0400 (EDT) In-Reply-To: <83364v5j28.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 10 Aug 2020 05:30:23 +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 00:02:07 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:253574 Archived-At: >> 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. > Could you please elaborate on your rationale for this? AFAIK the only use for it is debugging. In non-debugging contexts, font-lock-with-jit-lock should "always" give better behavior than font-lock-without-jit-lock. Stefan