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: Idea for syntax-ppss. Is it new? Could it be any good? Date: Sat, 26 Jul 2008 21:34:45 -0400 Message-ID: References: <20080726214429.GB3623@muc.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1217122516 14974 80.91.229.12 (27 Jul 2008 01:35:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 27 Jul 2008 01:35:16 +0000 (UTC) Cc: emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jul 27 03:36:06 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 1KMvB7-0007Zu-B5 for ged-emacs-devel@m.gmane.org; Sun, 27 Jul 2008 03:36:05 +0200 Original-Received: from localhost ([127.0.0.1]:39293 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KMvAC-0000gS-Rm for ged-emacs-devel@m.gmane.org; Sat, 26 Jul 2008 21:35:08 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KMv9y-0000YH-Hl for emacs-devel@gnu.org; Sat, 26 Jul 2008 21:34:54 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KMv9v-0000V2-AE for emacs-devel@gnu.org; Sat, 26 Jul 2008 21:34:52 -0400 Original-Received: from [199.232.76.173] (port=42344 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KMv9t-0000TE-TD for emacs-devel@gnu.org; Sat, 26 Jul 2008 21:34:50 -0400 Original-Received: from ironport2-out.pppoe.ca ([206.248.154.182]:28220 helo=ironport2-out.teksavvy.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KMv9s-000527-KB for emacs-devel@gnu.org; Sat, 26 Jul 2008 21:34:49 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aj0FAHVti0hFxIYw/2dsb2JhbACBW4k+onSBdA X-IronPort-AV: E=Sophos;i="4.31,257,1215403200"; d="scan'208";a="24848007" Original-Received: from 69-196-134-48.dsl.teksavvy.com (HELO pastel.home) ([69.196.134.48]) by ironport2-out.teksavvy.com with ESMTP; 26 Jul 2008 21:34:45 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 47A9D7F53; Sat, 26 Jul 2008 21:34:45 -0400 (EDT) In-Reply-To: <20080726214429.GB3623@muc.de> (Alan Mackenzie's message of "Sat, 26 Jul 2008 21:44:29 +0000") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. 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:101570 Archived-At: > How about reimplementing it thusly?: The current syntax would be cached > for positions at every N bytes (where N would be, perhaps 1024, possibly > 8192). A call to syntax-ppss would simply call parse-partial-sexp from > the latest valid cached position, filling out the cache as it goes. Any > buffer change would invalidate cached values for N > POS. Isn't that what syntax-ppss does? Stefan