From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Lennart Borgman (gmail)" Newsgroups: gmane.emacs.devel Subject: Re: [patch] use font-lock Date: Fri, 06 Jun 2008 09:24:46 +0200 Message-ID: <4848E63E.7040406@gmail.com> References: <200805231826.27371.danc@merrillpress.com> <200805271145.00741.danc@merrillpress.com> <200806051907.56862.danc@merrillpress.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1212737119 27741 80.91.229.12 (6 Jun 2008 07:25:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 6 Jun 2008 07:25:19 +0000 (UTC) Cc: Steve Yegge , Daniel Colascione , "Richard M. Stallman" , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jun 06 09:26:00 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 1K4WKl-0005gv-Jc for ged-emacs-devel@m.gmane.org; Fri, 06 Jun 2008 09:25:59 +0200 Original-Received: from localhost ([127.0.0.1]:54024 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K4WJy-0002iQ-Nn for ged-emacs-devel@m.gmane.org; Fri, 06 Jun 2008 03:25:10 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K4WJt-0002i8-QD for emacs-devel@gnu.org; Fri, 06 Jun 2008 03:25:05 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K4WJq-0002hT-0v for emacs-devel@gnu.org; Fri, 06 Jun 2008 03:25:05 -0400 Original-Received: from [199.232.76.173] (port=41073 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K4WJp-0002hQ-RH for emacs-devel@gnu.org; Fri, 06 Jun 2008 03:25:01 -0400 Original-Received: from mx20.gnu.org ([199.232.41.8]:31815) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1K4WJl-0005sL-5d; Fri, 06 Jun 2008 03:24:57 -0400 Original-Received: from ch-smtp02.sth.basefarm.net ([80.76.149.213]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K4WJk-0004m5-By; Fri, 06 Jun 2008 03:24:56 -0400 Original-Received: from c83-254-145-59.bredband.comhem.se ([83.254.145.59]:64055 helo=[127.0.0.1]) by ch-smtp02.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1K4WJi-0005Bk-7X; Fri, 06 Jun 2008 09:24:54 +0200 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.666 In-Reply-To: X-Antivirus: avast! (VPS 080606-0, 2008-06-06), Outbound message X-Antivirus-Status: Clean X-Originating-IP: 83.254.145.59 X-Scan-Result: No virus found in message 1K4WJi-0005Bk-7X. X-Scan-Signature: ch-smtp02.sth.basefarm.net 1K4WJi-0005Bk-7X c2fa5f063d3e6d4722e1d1db272bb139 X-detected-kernel: by mx20.gnu.org: Linux 2.6? (barebone, rare!) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) 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:98499 Archived-At: Stefan Monnier wrote: >>>>>> Addressed. See new version of the patch. >>>>> OK, let's wait for the paperwork, then. >>>> Great. :-) >>> The paperwork's in. >>> >>> Can you send a (hopefully) final version of your patch to emacs-devel so >>> someone can install it? > >> The last version I posted to the list is final. There are no issues I know >> about, and I've been using it myself. > > Can someone install it please? I do not think this can work with mumamo. Can you please wait with installing this? I have asked two times now if it works with mumamo, but unfortunately I have got no response so far. Please test if it does and also explain why it will work with mumamo. I have written an explanation of how fontifying parser could cooperate with font-lock, but it is not finished and I do not have time to send it right now. However my suggestions there seems to be in line with Steve Yegge's conclusion when he looked into this problem for js2.