From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Problems with syntax-ppss Date: Mon, 07 Apr 2008 12:43:21 -0400 Message-ID: References: <20080404172627.GB4804@muc.de> <47F69A4F.1050405@gmx.at> <20080405144642.GA3095@muc.de> <20080406140731.GA4084@muc.de> <47FA3A40.5080209@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1207586636 30946 80.91.229.12 (7 Apr 2008 16:43:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 7 Apr 2008 16:43:56 +0000 (UTC) Cc: Alan Mackenzie , emacs-devel@gnu.org, martin rudalics To: "Lennart Borgman \(gmail\)" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Apr 07 18:44:28 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JiuSD-0007Ou-6O for ged-emacs-devel@m.gmane.org; Mon, 07 Apr 2008 18:44:21 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JiuRa-0003Rn-3H for ged-emacs-devel@m.gmane.org; Mon, 07 Apr 2008 12:43:42 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JiuRW-0003Po-5Y for emacs-devel@gnu.org; Mon, 07 Apr 2008 12:43:38 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JiuRV-0003OR-F8 for emacs-devel@gnu.org; Mon, 07 Apr 2008 12:43:37 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JiuRV-0003OF-9t for emacs-devel@gnu.org; Mon, 07 Apr 2008 12:43:37 -0400 Original-Received: from 76-10-147-176.dsl.teksavvy.com ([76.10.147.176] helo=ceviche.home) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JiuRV-0000li-1h for emacs-devel@gnu.org; Mon, 07 Apr 2008 12:43:37 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id 18EEF70464; Mon, 7 Apr 2008 12:43:21 -0400 (EDT) In-Reply-To: <47FA3A40.5080209@gmail.com> (Lennart Borgman's message of "Mon, 07 Apr 2008 17:14:08 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:94592 Archived-At: >>> Would it not be a good idea to (i) redefine syntax-ppss as calculating >>> the syntax from BOB (as opposed to (point-min)); >> >> That's already what it does, when it can. Maybe it could be improved as >> follows: signal an error if it needs to recompute from (point-min) and >> (point-min) is not the beginning of the buffer, unless the caller sets >> a `syntax-ppss-narrowed-is-ok' variable (for use in modes like Info and >> Rmail). Maybe that variable should be shared with font-lock-dont-widen. > Until I had to start reading the code I thought that font-lock-dont-widen > already took care of this. I think there have to be a way to tell > syntax-ppss not to widen otherwise I can't see what purpose > font-lock-dont-widen could have (but I guess I am missing something there?). All I meant is that the two variables would probably always be set together: a mode that requires font-lock-dont-widen would also need syntax-ppss-narrowed-is-ok, so it might be better to link them somehow. Stefan