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: forward-comment and syntax-ppss Date: Fri, 16 Dec 2016 10:12:40 +0200 Message-ID: <83oa0c8f7r.fsf@gnu.org> References: <83fd1db0-7362-6117-c5cd-715398c0dea4@gmail.com> <20161207220447.GA4503@acm.fritz.box> <20161208201517.GB3120@acm.fritz.box> <20161209190747.GC2203@acm.fritz.box> <5a70902f-882e-f616-74b2-df6eb81fc70c@yandex.ru> <20161211101715.GA14084@acm.fritz.box> <51c0554f-40d0-37a5-b134-17058343aa3f@yandex.ru> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1481876041 20134 195.159.176.226 (16 Dec 2016 08:14:01 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 16 Dec 2016 08:14:01 +0000 (UTC) Cc: acm@muc.de, emacs-devel@gnu.org, monnier@iro.umontreal.ca, dgutov@yandex.ru To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Dec 16 09:13:57 2016 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 1cHneO-0004Od-Ac for ged-emacs-devel@m.gmane.org; Fri, 16 Dec 2016 09:13:56 +0100 Original-Received: from localhost ([::1]:58970 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cHneS-00055i-Ja for ged-emacs-devel@m.gmane.org; Fri, 16 Dec 2016 03:14:00 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46960) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cHndu-0004wt-8Z for emacs-devel@gnu.org; Fri, 16 Dec 2016 03:13:27 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cHndr-0003Xa-3r for emacs-devel@gnu.org; Fri, 16 Dec 2016 03:13:26 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:37736) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cHndr-0003XV-14; Fri, 16 Dec 2016 03:13:23 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2121 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1cHndq-0006wr-74; Fri, 16 Dec 2016 03:13:22 -0500 In-reply-to: (message from Drew Adams on Thu, 15 Dec 2016 18:06:09 -0800 (PST)) 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:210502 Archived-At: > Date: Thu, 15 Dec 2016 18:06:09 -0800 (PST) > From: Drew Adams > Cc: Stefan Monnier , emacs-devel@gnu.org > > > From where I'm standing, the things you use it for (hide > > buffer contents) > > No. Narrowing is not used to "hide buffer contents". That's not > the point of narrowing, even if it is one effect. It's used to > make some buffer contents inaccessible to certain (many, typical, > ordinary) operations. It is not just you who does not see parts > of the buffer; it is also Emacs features that do not perceive > them. Narrowing is used for both of these effects. One clear example of the former is Info mode, where the buffer is always narrowed to the current node.