Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion a problem with syntax highlighting in regexp.c

Received: by 10.68.27.1 with SMTP id p1mr1066203pbg.11.1310777129202;
        Fri, 15 Jul 2011 17:45:29 -0700 (PDT)
X-BeenThere: vim_dev@googlegroups.com
Received: by 10.68.59.41 with SMTP id w9ls1360904pbq.1.gmail; Fri, 15 Jul 2011
 17:45:26 -0700 (PDT)
Received: by 10.68.30.196 with SMTP id u4mr902923pbh.5.1310777126638;
        Fri, 15 Jul 2011 17:45:26 -0700 (PDT)
Received: by 10.68.30.196 with SMTP id u4mr902922pbh.5.1310777126629;
        Fri, 15 Jul 2011 17:45:26 -0700 (PDT)
Return-Path: <mail_ben_schm...@yahoo.com.au>
Received: from nm1.bullet.mail.sp2.yahoo.com (nm1.bullet.mail.sp2.yahoo.com [98.139.91.71])
        by gmr-mx.google.com with SMTP id a1si612001pbs.1.2011.07.15.17.45.25;
        Fri, 15 Jul 2011 17:45:25 -0700 (PDT)
Received-SPF: neutral (google.com: 98.139.91.71 is neither permitted nor denied by best guess record for domain of mail_ben_schm...@yahoo.com.au) client-ip=98.139.91.71;
Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 98.139.91.71 is neither permitted nor denied by best guess record for domain of mail_ben_schm...@yahoo.com.au) smtp.mail=mail_ben_schm...@yahoo.com.au; dkim=pass (test mode) header...@yahoo.com.au
Received: from [98.139.91.65] by nm1.bullet.mail.sp2.yahoo.com with NNFMP; 16 Jul 2011 00:45:25 -0000
Received: from [98.139.91.40] by tm5.bullet.mail.sp2.yahoo.com with NNFMP; 16 Jul 2011 00:45:25 -0000
Received: from [127.0.0.1] by omp1040.mail.sp2.yahoo.com with NNFMP; 16 Jul 2011 00:45:25 -0000
X-Yahoo-Newman-Id: 369731.27278...@omp1040.mail.sp2.yahoo.com
Received: (qmail 85682 invoked from network); 16 Jul 2011 00:45:24 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com.au;
  h=DKIM-Signature:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
  b=Z4RbVP3ildYJnC4Z5f1AUld2vTTntFNyTJqbjrt1vCzO+bYg1uC0ZqKiEDaNqBLB4Sqqs5cqb2GzPuNm1LCp05ee9sW6fdfWMmIu7CxKUEJDy/iPLPzFMH3VGbSJ8C6vbQ7LMU0CHFSvcCWLqb8g/aB/janmGRoiVOlwhpyCneA=  ;
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s1024; t=1310777124; bh=t+OauZXDFmf9BlBsylkn1e0A0UVfAa3zNDDTiZeDeBw=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=zo/tzp3pn8ZzdzBcndgtqKwr+O75XTVwkg1E+S3YDnKSQ782Ttv0PPkLvSE/bc+iZTJf3Duww8myo/dri07B/VtTV5ikT86p84Fb+cK/IVRWFcGCtD/rywwoQiF93GY7l5q3jmx2Ph+RQlDbVcBk2LbgCSeXPoT6YZtwyBZ6z+Q=
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: X4DZO2kVM1laiMLM1JLOi5zfnoTScr7Uh95CPK.M_EHUhqj
 29cV_MOUTo3mj1BOhhzzX560cOeTKjQ0ZVXPPUSACJOZXy__yu_E81msO2NL
 n6Qszo7254pXsZ5rf_6uESGQnJrAwKFlvoOio0nErajh7_ZyLPrCUjx.VTOW
 1Rj6cYVhBCPgnBfHalFfMn_T5OrTFiJbYhdxmusJ97OGaxF6TwrsxZ_jTHh0
 mm9LI5OiYfIh7OhcsnCN.6kAFHtyUJBNN2EpvpbcTLrrMPC9Vyetn7w7KQAr
 2ZAMK9TTMzOGpQKFf0sGJmKPJul_dj6M08AvOyhyzEyqfGukgk7yOh9EUCrg
 SS6oQRZFZLXkcCeQedBV6XfjEkQQ-
X-Yahoo-SMTP: enFMnPSswBAexaHyzgobwuUTrYOhZdJ0KRA2SjA-
Received: from thought.local (mail_ben_schm...@124.168.108.57 with plain)
        by smtp138.mail.mud.yahoo.com with SMTP; 15 Jul 2011 17:45:24 -0700 PDT
Message-ID: <4E20DF21.1070...@yahoo.com.au>
Date: Sat, 16 Jul 2011 10:45:21 +1000
From: Ben Schmidt <mail_ben_schm...@yahoo.com.au>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11 ThunderBrowse/3.3.5
MIME-Version: 1.0
To: vim_dev@googlegroups.com
CC: Charles Campbell <Charles.E.Campb...@nasa.gov>
Subject: Re: a problem with syntax highlighting in regexp.c
References: <4E1F366F.9050...@nasa.gov>
In-Reply-To: <4E1F366F.9050...@nasa.gov>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

> I extracted a couple of lines from regexp.c (143,144): (vim 7.3.244)
>
> #define BRANCH 3 /* node Match this alternative, or the
> * next... */
>
> and put them in a file "junk.c". Then
>
> vim -u NONE -N --noplugin junk.c
> :syn on
>
> shows the comment-ending pair of characters, */, in error highlighting.

No problem for me with Vim 7.3.219 and an updated syntax/c.vim which
hasn't made it into the official runtimes yet.

> FYI: I found this due to my looking at line 2045, (2044,2045)

No problems around that area for me either.

So, if it's a bug, it's a new one!

Ben.