From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Javier Oviedo" Newsgroups: gmane.emacs.help Subject: Re: custom C highlighting / syntax coloring Date: Wed, 19 Mar 2003 09:32:25 -0500 Organization: Texas Instruments Sender: help-gnu-emacs-bounces+gnu-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: References: NNTP-Posting-Host: main.gmane.org X-Trace: main.gmane.org 1048085270 18622 80.91.224.249 (19 Mar 2003 14:47:50 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 19 Mar 2003 14:47:50 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+gnu-help-gnu-emacs=m.gmane.org@gnu.org Wed Mar 19 15:47:47 2003 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18ver5-0004pp-00 for ; Wed, 19 Mar 2003 15:47:47 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18vepa-0008F1-02 for gnu-help-gnu-emacs@m.gmane.org; Wed, 19 Mar 2003 09:46:14 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!nntp.cs.ubc.ca!nntp-relay.ihug.net!ihug.co.nz!triton.net!smallfeed.triton.net!nntp1.hal-pc.org!attdl1!attdl2!ip.att.net!news.ti.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 53 Original-NNTP-Posting-Host: gt64v7121.telogy.design.ti.com Original-X-Trace: tilde.itg.ti.com 1048084258 9344 158.218.105.183 (19 Mar 2003 14:30:58 GMT) Original-X-Complaints-To: usenet@news.ti.com Original-NNTP-Posting-Date: 19 Mar 2003 14:30:58 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Original-Xref: shelby.stanford.edu gnu.emacs.help:111214 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: help-gnu-emacs-bounces+gnu-help-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.help:7714 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:7714 I use ctypes.el "Chris Pickett" wrote in message news:mailman.3348.1048030940.21513.help-gnu-emacs@gnu.org... > Hi, > > I like how CC Mode (for a .c or .h file) automatically recognizes words > ending in '_t' as being types and highlights them and the corresponding > declarations. However, I am working on a large project with several > other types. I need help customizing emacs to recognize these other > patterns as types. I find it makes understanding the source, which I > did not write, a lot easier. > > There are two classes: > > 1) most of the project-specific types start with '_svmt_' and so I would > like to recognize all of those, and have emacs color them. > > 2) several specific words such are also types, such as 'jboolean', > 'jint', 'jfloat', 'jobject', 'JNIEnv'. There's probably about 20 or > so. These are static and unlikely to change as the project changes ... > they are defined by the Java Native Interface specification. > > I managed to append '_t' to all words starting with '_svmt_', but the > other developers don't like that solution. It also doesn't solve the > problem for the second class of types. > > I looked at the CC Mode source, and I suppose I could define a whole > bunch more primitive types (solving problem number two), but I don't > know how to set that in my .emacs file. > > Finally, although this isn't really needed, it would be neat if the > highlighting worked only in certain directories. Maybe my .emacs file > could be modified to check for the presence of another highlighting file > in whatever directory emacs is currently in, and if found change the C > sub-mode (?) of CC Mode to recognize my extra types. > > Oh ... I'm using emacs 21.2.1, on 'woody' debian gnu/linux. > > Thanks very much, > Chris Pickett > > P.S. Please include my email address in the reply as I have not > subscribed to this list. > > P.P.S. I looked through the list archives and did about 1-2 hours of > searching / reading on Google, but still could not find anyone who had > tried to do this. > > >