From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: [SUSPECTED SPAM] Re: [Emacs-diffs] scratch/widen-less a4ba846: Replace prog-widen with consolidating widen calls Date: Thu, 30 Nov 2017 18:03:05 -0500 Message-ID: References: <20171129233237.27462.23351@vcs0.savannah.gnu.org> <20171129233238.504B5204F1@vcs0.savannah.gnu.org> <5d668ce5-1482-a3d4-c01b-7d996a532567@yandex.ru> <20171130214621.GA22157@ACM> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1512151659 3583 195.159.176.226 (1 Dec 2017 18:07:39 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 1 Dec 2017 18:07:39 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: emacs-devel@gnu.org, Tom Tromey , Vitalie Spinu , Dmitry Gutov To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Dec 01 19:07:35 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eKpim-0000XR-6O for ged-emacs-devel@m.gmane.org; Fri, 01 Dec 2017 19:07:32 +0100 Original-Received: from localhost ([::1]:59323 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eKpit-0004gR-1r for ged-emacs-devel@m.gmane.org; Fri, 01 Dec 2017 13:07:39 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47825) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eKoC2-0006k2-Qw for emacs-devel@gnu.org; Fri, 01 Dec 2017 11:29:40 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eKoBz-0005is-D3 for emacs-devel@gnu.org; Fri, 01 Dec 2017 11:29:38 -0500 Original-Received: from pmta11.teksavvy.com ([76.10.157.34]:9596) by eggs.gnu.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.71) (envelope-from ) id 1eKoBz-0005hr-6o for emacs-devel@gnu.org; Fri, 01 Dec 2017 11:29:35 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2HpoADzjCBa/1rWbkFbHQEBBQELAYM8g?= =?us-ascii?q?VSDW4ptco4BAYF8FCABlkKCEAqFNQQCAoUgSw0BAQEBAQEBAQEDaCiFIQEEAVY?= =?us-ascii?q?jBQsLDiYSFBgNJC6JfwioS4pnAQEIAiaDQYhzixgBBJMUj0ehCYdblkWBOk0Mg?= =?us-ascii?q?VEyGggwgmSDBoFsI4o7AQEB?= X-IPAS-Result: =?us-ascii?q?A2HpoADzjCBa/1rWbkFbHQEBBQELAYM8gVSDW4ptco4BAYF?= =?us-ascii?q?8FCABlkKCEAqFNQQCAoUgSw0BAQEBAQEBAQEDaCiFIQEEAVYjBQsLDiYSFBgNJ?= =?us-ascii?q?C6JfwioS4pnAQEIAiaDQYhzixgBBJMUj0ehCYdblkWBOk0MgVEyGggwgmSDBoF?= =?us-ascii?q?sI4o7AQEB?= X-IronPort-AV: E=Sophos;i="5.45,343,1508817600"; d="scan'208";a="10858677" Original-Received: from 65-110-214-90.cpe.pppoe.ca (HELO fmsmemgm.homelinux.net) ([65.110.214.90]) by smtp.teksavvy.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Nov 2017 18:03:05 -0500 Original-Received: by fmsmemgm.homelinux.net (Postfix, from userid 20848) id 7FFEEAE55C; Thu, 30 Nov 2017 18:03:05 -0500 (EST) In-Reply-To: <20171130214621.GA22157@ACM> (Alan Mackenzie's message of "Thu, 30 Nov 2017 21:46:21 +0000") X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 76.10.157.34 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:220568 Archived-At: > Using narrowing for marking the bounds of a sub-mode is a bad thing, > since it is likely to cause contention with other uses of narrowing. Dmitry's solution to this threat is to say that indent-line-function should always be called fully-widened, so there can be no "other uses of narrowing" that can get in the way. > It's not clear what is meant here, but mandating maintainers of major > modes to use narrowing in a particular way is at best controversial, and > probably will render many major modes non-functional. It doesn't mandate that major modes use narrowing. Quite the opposite: it says "don't touch narrowing inside your indentation function (unless you know what you're doing), because it's already setup for you". Stefan