From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [Emacs-diffs] scratch/widen-less a4ba846: Replace prog-widen with consolidating widen calls Date: Tue, 05 Dec 2017 17:53:00 +0000 Message-ID: <6A58664C-42E7-48E4-BB90-0488FED4A7FD@gnu.org> References: <20171129233237.27462.23351@vcs0.savannah.gnu.org> <5d668ce5-1482-a3d4-c01b-7d996a532567@yandex.ru> <20171130214621.GA22157@ACM> <27985594-3bb4-ce88-8928-2ccfeac13eae@yandex.ru> <20171201154913.GB3840@ACM> <1e542021-e389-cca4-6acd-349efddb2652@yandex.ru> <20171201223529.GG3840@ACM> <4a94ec5c-efdd-50f1-ff4d-277f5f45c2df@yandex.ru> <83lgil1qme.fsf@gnu.org> <83d13x1j2s.fsf@gnu.org> <34abea95-c7f7-e8fa-8407-8c2fd2a4cfe1@yandex.ru> <83y3mkzw1n.fsf@gnu.org> <83mv2zzv7z.fsf@gnu.org> <83r2saxyj1.fsf@gnu.org> <83efoaxv0c.fsf@gnu.org> <57382399-5efa-655f-e374-fbe1ef9d89aa@yandex.ru> <27732BB8-B3B7-4489-963E-A09333026A8E@gnu.org> <43ec332a-4de5-d3ce-1bc2-60b081447f77@yandex.ru> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1512496448 28669 195.159.176.226 (5 Dec 2017 17:54:08 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 5 Dec 2017 17:54:08 +0000 (UTC) User-Agent: K-9 Mail for Android To: Dmitry Gutov , emacs-devel@gnu.org, Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 05 18:53:58 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 1eMHPk-0006p8-RS for ged-emacs-devel@m.gmane.org; Tue, 05 Dec 2017 18:53:52 +0100 Original-Received: from localhost ([::1]:51424 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eMHPs-00036h-7n for ged-emacs-devel@m.gmane.org; Tue, 05 Dec 2017 12:54:00 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57699) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eMHPL-00036R-5b for emacs-devel@gnu.org; Tue, 05 Dec 2017 12:53:28 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eMHPG-0000FQ-B1 for emacs-devel@gnu.org; Tue, 05 Dec 2017 12:53:27 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:53604) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eMHP2-0000CC-M7; Tue, 05 Dec 2017 12:53:08 -0500 Original-Received: from [176.12.136.31] (port=50049 helo=[10.208.45.224]) by fencepost.gnu.org with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1eMHP1-0000R3-OG; Tue, 05 Dec 2017 12:53:08 -0500 In-Reply-To: <43ec332a-4de5-d3ce-1bc2-60b081447f77@yandex.ru> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e 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:220744 Archived-At: On December 5, 2017 10:55:33 AM GMT+00:00, Dmitry Gutov wrote: > On 12/5/17 7:33 AM, Eli Zaretskii wrote: >=20 > > And btw, I'm not really convinced the unconditional widening is a > good idea in general, even on master=2E I could probably agree that in > most cases it is TRT, but why would we _force_ all modes to indent > with restrictions lifted? No exceptions? Not even a fire escape for > some specialized mode with weird needs and requirements? I'm not > sure=2E It certainly should be discussed, regardless of the MMM issues= =2E >=20 > After indent-for-tab-command calls widen, indent-line-function is=20 > called=2E And it can apply all the narrowing it wants (inside=20 > save-restriction), it just shouldn't call 'widen'=2E You assume that the indentation function has the same information about th= e higher-level context as its callers=2E But that assumption is not necess= arily true; narrowing exists precisely because higher-level code wants to s= et up lower-level code without explicitly passing it this information=2E