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: New paren matching feature request Date: Fri, 30 Jan 2009 20:39:35 -0500 Message-ID: References: <31628377.61031233245050005.JavaMail.www@wwinf4614> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1233366010 23818 80.91.229.12 (31 Jan 2009 01:40:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 31 Jan 2009 01:40:10 +0000 (UTC) Cc: alinsoar@voila.fr, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 31 02:41:23 2009 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 1LT4rG-0002aM-8N for ged-emacs-devel@m.gmane.org; Sat, 31 Jan 2009 02:41:20 +0100 Original-Received: from localhost ([127.0.0.1]:58439 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LT4pw-0004AM-IM for ged-emacs-devel@m.gmane.org; Fri, 30 Jan 2009 20:39:56 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LT4ps-00049O-Dv for emacs-devel@gnu.org; Fri, 30 Jan 2009 20:39:52 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LT4pq-00046p-0P for emacs-devel@gnu.org; Fri, 30 Jan 2009 20:39:51 -0500 Original-Received: from [199.232.76.173] (port=39008 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LT4pp-00046m-SZ for emacs-devel@gnu.org; Fri, 30 Jan 2009 20:39:49 -0500 Original-Received: from ironport2-out.pppoe.ca ([206.248.154.182]:36012 helo=ironport2-out.teksavvy.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LT4pk-0007g6-6N; Fri, 30 Jan 2009 20:39:44 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsYEAEc6g0nO+IQk/2dsb2JhbACBbshHhBEGglU X-IronPort-AV: E=Sophos;i="4.37,354,1231131600"; d="scan'208";a="33086027" Original-Received: from 206-248-132-36.dsl.teksavvy.com (HELO pastel.home) ([206.248.132.36]) by ironport2-out.teksavvy.com with ESMTP; 30 Jan 2009 20:39:35 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 243208229; Fri, 30 Jan 2009 20:39:35 -0500 (EST) In-Reply-To: (Richard M. Stallman's message of "Fri, 30 Jan 2009 02:25:30 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-operating-system: 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:108429 Archived-At: > I have a feeling that the right way to do this kind of colorization > is through Font Lock mode, and that the hardest part of the job > is hooking it up to the structure of jit-lock. I agree and I also think that Alin's right in that the best way to do it is via parse-partial-sexp (suitably enhanced if/as needed). Font-lock-mode already uses parse-partial-sexp to do comment&string highlighting. Stefan