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: Thu, 13 Aug 2020 10:00:37 -0400 Message-ID: References: <83364v5j28.fsf@gnu.org> <83y2mm4n07.fsf@gnu.org> <83ft8t43og.fsf@gnu.org> <835z9noh13.fsf@gnu.org> <831rkboez0.fsf@gnu.org> <83a6yymzvy.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="7571"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Stefan Kangas , 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 Thu Aug 13 16:02:11 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 1k6Do2-0001nB-S2 for ged-emacs-devel@m.gmane-mx.org; Thu, 13 Aug 2020 16:02:10 +0200 Original-Received: from localhost ([::1]:45584 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k6Do1-0007Pc-Rf for ged-emacs-devel@m.gmane-mx.org; Thu, 13 Aug 2020 10:02:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42874) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k6Dme-0006hk-7L for emacs-devel@gnu.org; Thu, 13 Aug 2020 10:00:44 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:55359) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k6Dmc-0007C6-7R; Thu, 13 Aug 2020 10:00:43 -0400 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 9B997809C8; Thu, 13 Aug 2020 10:00:40 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id CAD2A80581; Thu, 13 Aug 2020 10:00:38 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1597327238; bh=y1K+yGOGVYk1VKEbrFFMAZImGhIJJmVzyuuTZZaL5Mk=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=f9Sk1kuiVR4M/UkYjO+CuR+Z9yLK3G7TjolKI5GcmesWM6iFPQ2J9MGJPyjzsBBlX QVZ933hwsUOwFL4cWIroiq9LSvyjGTcTina0K1wzOB+tC1T4cYJIGm039Zx9PnBdm7 meQQj7SXE8qcX0cYHH16HG0djAVdnombiycmESRDBeO1DK4gLshQG9OHqE1Sx1FqIb D6pEIwrAD+b4m1uoRI2sTXwMUWkqOhQlmMHZYi9JJR98FBZ7JZLbn11STBS25mZQWu dTb0scNITvgor7jS5zBzeSNS8xFMv4Faul7qTbDgR9JPKM8HbdtZMLKlY8UWGlNgTT TVS+i5RniQZtw== Original-Received: from alfajor (unknown [45.72.246.108]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 97A131204E7; Thu, 13 Aug 2020 10:00:38 -0400 (EDT) In-Reply-To: <83a6yymzvy.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 13 Aug 2020 16:36:17 +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/13 09:33:20 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:253731 Archived-At: > Sorry for not being more clear. I meant deleting > font-lock-support-mode: it must be declared obsolete first (which > would require adding the command proposed by Stefan), Agreed. > then, after some obsolescence time, we could delete > font-lock-support-mode, and then we can delete fast-lock and > fuzzy-lock. Disagreed. I don't see any reason why we should wait for `font-lock-support-mode` to disappear before we can get rid of those two packages that have been officially obsoleted for so many years already. Stefan