From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Rob Hutten" Newsgroups: gmane.emacs.help Subject: font-lock issue with cpp syntax highlighting Date: Thu, 29 Jan 2009 16:58:17 -0400 Message-ID: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C98254.500AFFE4" X-Trace: ger.gmane.org 1233289507 15956 80.91.229.12 (30 Jan 2009 04:25:07 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 30 Jan 2009 04:25:07 +0000 (UTC) To: Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Jan 30 05:26:21 2009 Return-path: Envelope-to: geh-help-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 1LSkxQ-0001Kn-Lx for geh-help-gnu-emacs@m.gmane.org; Fri, 30 Jan 2009 05:26:21 +0100 Original-Received: from localhost ([127.0.0.1]:44604 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LSkw8-0003mW-DU for geh-help-gnu-emacs@m.gmane.org; Thu, 29 Jan 2009 23:25:00 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LSeHM-0005ow-9m for help-gnu-emacs@gnu.org; Thu, 29 Jan 2009 16:18:28 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LSeHL-0005oM-0w for help-gnu-emacs@gnu.org; Thu, 29 Jan 2009 16:18:27 -0500 Original-Received: from [199.232.76.173] (port=52694 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LSeHK-0005oD-Kw for help-gnu-emacs@gnu.org; Thu, 29 Jan 2009 16:18:26 -0500 Original-Received: from mail1.flagstonere.bm ([72.28.72.17]:1491 helo=hfxmim01.westend.bm) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LSeHK-0007YU-73 for help-gnu-emacs@gnu.org; Thu, 29 Jan 2009 16:18:26 -0500 Original-Received: from hfxexc001.flagstonere.local (hfxexc001.flagstonere.local) by hfxmim01.westend.bm (Clearswift SMTPRS 5.2.9) with ESMTP id for ; Thu, 29 Jan 2009 16:58:41 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: font-lock issue with cpp syntax highlighting Thread-Index: AcmCVE9J66xqjQpNRiiR+fNSoxHAxg== X-detected-operating-system: by monty-python.gnu.org: Windows XP SP1+, 2000 SP3 (2) X-Greylist: delayed 1212 seconds by postgrey-1.27 at monty-python; Thu, 29 Jan 2009 16:18:23 EST X-Mailman-Approved-At: Thu, 29 Jan 2009 23:22:01 -0500 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:61772 Archived-At: This is a multi-part message in MIME format. ------_=_NextPart_001_01C98254.500AFFE4 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, =20 Apologies if this is a newbie question. A few of us here have combed list archives and the next in general but cannot find an answer to our question. =20 We have two development environments in which our coder uses emacs: =20 Old: emacs-21.3.1 on RHEL4 =20 New: emacs-21.4.1 on CentOS 5.2 =20 Both environments share the same cpp.elc and jackknife environment files. Yet the syntax highlighting for C++ code seems to be using different parsing rules; we understand how to map colours to certain syntactical elements, but we're in the dark as to exactly how the C++-specific syntactical elements (i.e. constants, types, namespaces, etc.) are defined. =20 If some kind soul could help shed a little light here, we'd be very grateful. =20 -Rob =20 =20 ********************************************************************** This communication contains information which is confidential and may also = be legally privileged. It is for the exclusive use of the intended recipien= t(s). If you are not the intended recipient(s), disclosure, copying, distri= bution, or other use of, or action taken or omitted to be taken in reliance= upon, this communication or the information in it is prohibited and maybe = unlawful. If you have received this communication in error please notify th= e sender by return email, delete it from your system and destroy any copies. ********************************************************************** ------_=_NextPart_001_01C98254.500AFFE4 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

Apologies if this is a newbie question.  A few of= us here have combed list archives and the next in general but cannot find an answer= to our question.

 

We have two development environments in which our code= r uses emacs:

 

Old:  emacs-21.3.1 on RHEL4

 

New: emacs-21.4.1 on CentOS 5.2

 

Both environments share the same cpp.elc and jackknife environment files.  Yet the syntax highlighting for C++ code seems to = be using different parsing rules; we understand how to map colours to certain syntactical elements, but we're in the dark as to exactly how the C++-speci= fic syntactical elements (i.e. constants, types, namespaces, etc.) are defined.=

 

If some kind soul could help shed a little light here,= we'd be very grateful.

 

-Rob

 

 

*********************= *************************************************

This communication co= ntains information which is confidential and may also be legally privileged= . It is for the exclusive use of the intended recipient(s). If you are not = the intended recipient(s), disclosure, copying, distribution, or other use = of, or action taken or omitted to be taken in reliance upon, this communica= tion or the information in it is prohibited and maybe unlawful. If you have= received this communication in error please notify the sender by return em= ail, delete it from your system and destroy any copies.

*********************= *************************************************

 

------_=_NextPart_001_01C98254.500AFFE4--