From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.bugs Subject: bug#1913: Identifier after reserved word "raise" is not always highlighted in Ada-mode Date: Fri, 16 Jan 2009 00:10:44 +0100 Message-ID: References: <496EECEB.1020209@gmail.com> <496F3CE6.3080600@gmail.com> <496FC0B1.3020207@gmail.com> Reply-To: Juanma Barranquero , 1913@emacsbugs.donarmstrong.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1232061904 14992 80.91.229.12 (15 Jan 2009 23:25:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 15 Jan 2009 23:25:04 +0000 (UTC) Cc: 1913@emacsbugs.donarmstrong.com To: Erik Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Jan 16 00:26:16 2009 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LNbbC-0001HL-Ge for geb-bug-gnu-emacs@m.gmane.org; Fri, 16 Jan 2009 00:26:07 +0100 Original-Received: from localhost ([127.0.0.1]:40721 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LNbZv-0003LQ-2K for geb-bug-gnu-emacs@m.gmane.org; Thu, 15 Jan 2009 18:24:47 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LNbYn-0002Ea-3w for bug-gnu-emacs@gnu.org; Thu, 15 Jan 2009 18:23:37 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LNbYj-0002Av-La for bug-gnu-emacs@gnu.org; Thu, 15 Jan 2009 18:23:35 -0500 Original-Received: from [199.232.76.173] (port=59313 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LNbYi-0002AL-QA for bug-gnu-emacs@gnu.org; Thu, 15 Jan 2009 18:23:32 -0500 Original-Received: from rzlab.ucr.edu ([138.23.92.77]:54716) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LNbYh-0008VT-Dd for bug-gnu-emacs@gnu.org; Thu, 15 Jan 2009 18:23:32 -0500 Original-Received: from rzlab.ucr.edu (rzlab.ucr.edu [127.0.0.1]) by rzlab.ucr.edu (8.13.8/8.13.8/Debian-3) with ESMTP id n0FNNQJa026463; Thu, 15 Jan 2009 15:23:27 -0800 Original-Received: (from debbugs@localhost) by rzlab.ucr.edu (8.13.8/8.13.8/Submit) id n0FNF7P2024026; Thu, 15 Jan 2009 15:15:07 -0800 X-Loop: owner@emacsbugs.donarmstrong.com Resent-From: Juanma Barranquero Resent-To: bug-submit-list@donarmstrong.com Resent-CC: Emacs Bugs , owner@emacsbugs.donarmstrong.com Resent-Date: Thu, 15 Jan 2009 23:15:07 +0000 Resent-Message-ID: Resent-Sender: owner@emacsbugs.donarmstrong.com X-Emacs-PR-Message: followup 1913 X-Emacs-PR-Package: emacs,ada-mode X-Emacs-PR-Keywords: Original-Received: via spool by 1913-submit@emacsbugs.donarmstrong.com id=B1913.123206104823451 (code B ref 1913); Thu, 15 Jan 2009 23:15:07 +0000 Original-Received: (at 1913) by emacsbugs.donarmstrong.com; 15 Jan 2009 23:10:48 +0000 X-Spam-Bayes: score:0.5 Bayes not run. spammytokens:Tokens not available. hammytokens:Tokens not available. Original-Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27]) by rzlab.ucr.edu (8.13.8/8.13.8/Debian-3) with ESMTP id n0FNAiFH023444 for <1913@emacsbugs.donarmstrong.com>; Thu, 15 Jan 2009 15:10:46 -0800 Original-Received: by ey-out-2122.google.com with SMTP id 4so161310eyf.13 for <1913@emacsbugs.donarmstrong.com>; Thu, 15 Jan 2009 15:10:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=X6jidzMFs7RZbbpN7mfC2GfFvVNAFEr3jGgGKGjTAI4=; b=ZiQ1yHoTARR5DaVK+n/Q6QGYjdWSVMjQsEkmfguMeMeHvMG+wPEc4pKki8+h791KUH 6JDvBkuVWF2CZgjEBKNWRCZUlnwOnPgcmwTpxemXVv1IDU8L5L3X1im6f3qxn4Tk9UVU yNcgVb5RSpDH2Gri0THVyr20CGY2kH7b2onGY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=XTz1zKE1PU21Xvl6jz2mNEjyo5wr/6IUSjwX1dLEjM8FR508J7QqbfD7NtFHlDDHGa qfXdqi6IKUSbxuecGPy7SiBSwE1FxkEoCsCoGzE1nwCno+j5EYRd9s6i3Wd0zKMvzIn2 ZJ7biPP5Y/Vz8keWbmarZdMpa4LBO6b4i4h7c= Original-Received: by 10.210.131.6 with SMTP id e6mr293578ebd.77.1232061044058; Thu, 15 Jan 2009 15:10:44 -0800 (PST) In-Reply-To: <496FC0B1.3020207@gmail.com> X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) Resent-Date: Thu, 15 Jan 2009 18:23:35 -0500 X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:24175 Archived-At: On Fri, Jan 16, 2009 at 00:03, Erik wrote: > Actually I do notice the highlighting and take advantage of it as an > early error detector. If it makes me notice an error immediately, before > I move on to another part of the code or try to compile things, it is > useful. If a word is not highlighted as expected when I have typed it, I > automatically stop to see what I did wrong. But we're not talking of something that is highlighted "when you move to another part of the code"; more like "when you finish the next token in the line". > Did you have a performance problem with that regexp? I do not really > believe that there is a reason to worry about it without some > measurements. I have a 1.6 GHz CPU and want to take advantage of it. I > think it should be able to recognize Ada identifiers as a type them. I don't have a performance problem, but font-locking isn't the fastest of Emacs features. You have a 1,6 GHz CPU; mine is fast, too. But Emacs is used in all kinds of computers. That said, if you write a patch to make the font-locking more correct without sacrificing performance, I'm sure it'll be very welcome. > The (?:) is equivalent to () but faster since it is a so-called > non-capturing group, which should always be used when capturing is not > needed. Maybe that helps? Not really. Font-lock patterns have capturing groups for a reason (that's what the 1, 2 in the next line refer to). Juanma