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: Re: [SUSPECTED SPAM] Re: [Emacs-diffs] scratch/widen-less a4ba846: Replace prog-widen with consolidating widen calls Date: Thu, 14 Dec 2017 09:32:27 -0500 Message-ID: References: <20171129233237.27462.23351@vcs0.savannah.gnu.org> <83o9nexy48.fsf@gnu.org> <83d13uxug5.fsf@gnu.org> <41e3f343-816f-d2db-6575-6ef43d54957f@yandex.ru> <838tecuqjb.fsf@gnu.org> <83609etizl.fsf@gnu.org> <83wp1ts123.fsf@gnu.org> <1e8587a7-c98b-5183-3cfd-8e1034443f44@yandex.ru> <83shchrwia.fsf@gnu.org> <83lgi9ruo8.fsf@gnu.org> <01c15d4e-566b-3b7f-c4e6-6f199ba5bcc3@yandex.ru> <89c4a839-a124-a1a8-5cf9-583baf2b4dd6@yandex.ru> <7e4799f9-b640-f363-5ecc-3b83eeada292@yandex.ru> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1513262134 10598 195.159.176.226 (14 Dec 2017 14:35:34 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 14 Dec 2017 14:35:34 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Dec 14 15:35:31 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 1ePUbi-0002Rg-Sj for ged-emacs-devel@m.gmane.org; Thu, 14 Dec 2017 15:35:30 +0100 Original-Received: from localhost ([::1]:41272 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ePUbn-0002Em-1T for ged-emacs-devel@m.gmane.org; Thu, 14 Dec 2017 09:35:35 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42719) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ePUYz-0000q1-Fg for emacs-devel@gnu.org; Thu, 14 Dec 2017 09:32:47 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ePUYv-0004Ex-Ee for emacs-devel@gnu.org; Thu, 14 Dec 2017 09:32:41 -0500 Original-Received: from [195.159.176.226] (port=54678 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ePUYv-0004CX-5f for emacs-devel@gnu.org; Thu, 14 Dec 2017 09:32:37 -0500 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1ePUYk-0002Kp-FP for emacs-devel@gnu.org; Thu, 14 Dec 2017 15:32:26 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 26 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:LRzLsezujpodbkRU30IMz59iTOM= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 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:221055 Archived-At: >> Maybe some of the doc should be in the narrowing section, where we can >> document the contexts where the narrowing is "guaranteed" >> (e.g. font-lock and indentation). > Hmm. Currently, that page doesn't exactly describe when one should call > 'widen', and when shouldn't. [ I don't think in those terms: with the new convention, an indent-line-function still can call widen as much as it wants, it just doesn't need to and probably doesn't want to. ] No, indeed, it doesn't talk about the different uses of narrowing. It probably should say something, tho, especially w.r.t this new convention. > Also, the piece of documentation I'm thinking about will probably need to > reference, again, "Some major modes need to support embedded regions of text > whose > syntax belongs to a different major mode. Examples include “literate > programming” source files that combine documentation and snippets of > source code..."; maybe that introduction should leave the Indentation > Controlled by Major Mode section, and get a section of its own. Makes sense. And then refer to it from the narrowing section, indentation section, etc... Stefan