From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Daniel Colascione Newsgroups: gmane.emacs.devel Subject: Re: Why js2-mode in Emacs 23.2? Date: Sun, 9 Aug 2009 19:58:16 -0400 Message-ID: References: <7b501d5c0908091634ndfba631vd9db6502db301097@mail.gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1249862317 28446 80.91.229.12 (9 Aug 2009 23:58:37 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 9 Aug 2009 23:58:37 +0000 (UTC) Cc: Emacs-Devel devel To: Lennart Borgman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 10 01:58:30 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 1MaIHV-0004Xf-GL for ged-emacs-devel@m.gmane.org; Mon, 10 Aug 2009 01:58:30 +0200 Original-Received: from localhost ([127.0.0.1]:44669 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaIHU-0000ni-Hd for ged-emacs-devel@m.gmane.org; Sun, 09 Aug 2009 19:58:28 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaIHQ-0000nR-3w for emacs-devel@gnu.org; Sun, 09 Aug 2009 19:58:24 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaIHL-0000jg-3E for emacs-devel@gnu.org; Sun, 09 Aug 2009 19:58:23 -0400 Original-Received: from [199.232.76.173] (port=41752 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaIHK-0000jZ-UG for emacs-devel@gnu.org; Sun, 09 Aug 2009 19:58:18 -0400 Original-Received: from vpn.merrillpress.com ([64.61.107.78]:50299) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MaIHK-0007nn-Dz for emacs-devel@gnu.org; Sun, 09 Aug 2009 19:58:18 -0400 Original-Received: from cpe-67-246-181-235.buffalo.res.rr.com ([67.246.181.235] helo=[192.168.1.103]) by mars.merrillpress.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.63) (envelope-from ) id 1MaIHJ-0002nB-L4; Sun, 09 Aug 2009 19:58:17 -0400 In-Reply-To: X-Mailer: Apple Mail (2.936) X-detected-operating-system: by monty-python.gnu.org: GNU/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:113902 Archived-At: On Aug 9, 2009, at 7:55 PM, Lennart Borgman wrote: > It is up to Chong and Stefan of course. Of course. > Could you please make sure espresso-mode follows Emacs conventions? I > am not sure but I think there were some thing that could be fixed. The only issue I'm aware of is that espresso-mode syntactically fontifies the whole buffer when starting up to ensure that regular expressions are marked correctly. The comment that explains it is here: ;; Important to fontify the whole buffer syntactically! If we don't, ;; then we might have regular expression literals that aren't marked ;; as strings, which will screw up parse-partial-sexp, scan-lists, ;; etc. and and produce maddening "unbalanced parenthesis" errors. ;; When we attempt to find the error and scroll to the portion of ;; the buffer containing the problem, JIT-lock will apply the ;; correct syntax to the regular expresion literal and the problem ;; will mysteriously disappear.