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: Bug #25608 and the comment-cache branch Date: Mon, 13 Feb 2017 21:34:12 +0200 Message-ID: <83bmu528cr.fsf@gnu.org> References: <20170202202418.GA2505@acm> <83lgtouxpf.fsf@gnu.org> <20170202215154.GB2505@acm> <83h94bvhzw.fsf@gnu.org> <20170205220045.GB2294@acm> <83d1es61li.fsf@gnu.org> <20170211232511.GA13712@acm> <20170212120553.GB3087@acm> <20170213180919.GA2377@acm> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1487014452 26595 195.159.176.226 (13 Feb 2017 19:34:12 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 13 Feb 2017 19:34:12 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 13 20:34:07 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 1cdMNy-0006XN-NN for ged-emacs-devel@m.gmane.org; Mon, 13 Feb 2017 20:34:06 +0100 Original-Received: from localhost ([::1]:59197 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cdMO4-0007WX-Ea for ged-emacs-devel@m.gmane.org; Mon, 13 Feb 2017 14:34:12 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38871) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cdMNu-0007Ux-Dw for emacs-devel@gnu.org; Mon, 13 Feb 2017 14:34:03 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cdMNq-0000Fq-GL for emacs-devel@gnu.org; Mon, 13 Feb 2017 14:34:02 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:35444) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cdMNq-0000Fm-D1; Mon, 13 Feb 2017 14:33:58 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1873 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1cdMNp-0008Ou-BX; Mon, 13 Feb 2017 14:33:58 -0500 In-reply-to: <20170213180919.GA2377@acm> (message from Alan Mackenzie on Mon, 13 Feb 2017 18:09:19 +0000) 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:212348 Archived-At: > Date: Mon, 13 Feb 2017 18:09:19 +0000 > From: Alan Mackenzie > Cc: emacs-devel@gnu.org > > Both the Lisp and C parts of Emacs use narrowing and widening "all > the time" Are you sure? In C code, I see exactly 2 calls to 'widen' and 4 calls to 'narrow-to-region', something that doesn't really fit "all the time" description. (Most of the above few calls are to support auto-saving and process-filters, and the rest are in set-buffer-multibyte -- it should be clear to anyone that all of the above must override any narrowing.)