From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.devel Subject: Re: forward-comment and syntax-ppss Date: Thu, 8 Dec 2016 19:31:03 +0000 Message-ID: <20161208193103.GA3120@acm.fritz.box> References: <20161206195507.GA2996@acm.fritz.box> <83fd1db0-7362-6117-c5cd-715398c0dea4@gmail.com> <20161207220447.GA4503@acm.fritz.box> <2b1c72b9-8d69-5b93-26dc-7f51c5683d0c@gmail.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1481225529 1564 195.159.176.226 (8 Dec 2016 19:32:09 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 8 Dec 2016 19:32:09 +0000 (UTC) User-Agent: Mutt/1.5.24 (2015-08-30) Cc: emacs-devel@gnu.org To: =?iso-8859-1?Q?Cl=E9ment?= Pit--Claudel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Dec 08 20:32:04 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 1cF4QG-000859-4U for ged-emacs-devel@m.gmane.org; Thu, 08 Dec 2016 20:32:04 +0100 Original-Received: from localhost ([::1]:48428 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cF4QJ-0002eI-P2 for ged-emacs-devel@m.gmane.org; Thu, 08 Dec 2016 14:32:07 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37234) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cF4Ph-0002dl-FO for emacs-devel@gnu.org; Thu, 08 Dec 2016 14:31:30 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cF4Pe-0007yg-CW for emacs-devel@gnu.org; Thu, 08 Dec 2016 14:31:29 -0500 Original-Received: from ocolin.muc.de ([193.149.48.4]:25988 helo=mail.muc.de) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1cF4Pe-0007wH-14 for emacs-devel@gnu.org; Thu, 08 Dec 2016 14:31:26 -0500 Original-Received: (qmail 18799 invoked by uid 3782); 8 Dec 2016 19:31:24 -0000 Original-Received: from acm.muc.de (p548C7568.dip0.t-ipconnect.de [84.140.117.104]) by colin.muc.de (tmda-ofmipd) with ESMTP; Thu, 08 Dec 2016 20:31:23 +0100 Original-Received: (qmail 3200 invoked by uid 1000); 8 Dec 2016 19:31:03 -0000 Content-Disposition: inline In-Reply-To: <2b1c72b9-8d69-5b93-26dc-7f51c5683d0c@gmail.com> X-Delivery-Agent: TMDA/1.1.12 (Macallan) X-Primary-Address: acm@muc.de X-detected-operating-system: by eggs.gnu.org: FreeBSD 9.x [fuzzy] X-Received-From: 193.149.48.4 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:210147 Archived-At: Hello, Clément. On Wed, Dec 07, 2016 at 05:23:42PM -0500, Clément Pit--Claudel wrote: > On 2016-12-07 17:04, Alan Mackenzie wrote: > > You haven't seen "many" issues about syntax-ppss? One is enough, if > > it's bad enough. Read up on bug #22983. > Thanks, Alan. I remember reading this long thread a while ago, though > some of the stuff I had trouble following. > Stefan and you are in a better position than I am to assess the > significance of that issue. The only data point that I can share is > that I've found multiple packages to be broken by narrowing, to the > point that I don't use narrowing any more. That's tragic. You clearly wanted to use narrowing, yet some bug, quite likely to be #22983, made narrowing such a bad experience that you stopped using it. Did you raise any bug reports for these failures? > Instead, I use a less invasive solution with two invisible overlays > covering 1..(beginning of narrowed region) and (end of narrowed > region)..(buffer-size). Narrowing isn't "invasive", whatever that means. It's such a natural and useful feature that it's surprising other editors haven't got it too. It's the pertinent bug (likely to be #22983) which has screwed up code when narrowing is used which is at fault, not narrowing itself. > Some packages use (point-min) when they really mean 1 (or, if one > prefers, (save-restriction (widen) (point-min))), .... I prefer a simple 1 myself. > .... and things start breaking in the presence of narrowing; so > basically, I don't really expect things to work smoothly when I use > narrowing, and so I don't use it. If things stopped working for me with narrowing, I'd be over the top with rage. I use narrowing all the time. I think it's time to fix some bugs, and hopefully persuade you that narrowing _can_ be used usefully. > Clément. -- Alan Mackenzie (Nuremberg, Germany).