From: Matthew Kennedy <mbkennedy@austin.rr.com>
Subject: Re: custom C highlighting / syntax coloring
Date: Wed, 19 Mar 2003 16:19:39 GMT [thread overview]
Message-ID: <8765qfcoqo.fsf@killr.ath.cx> (raw)
In-Reply-To: trllzb9zes.fsf@coyote.llan.ll.mit.edu
Peter Boettcher <boettcher@ll.mit.edu> writes:
> [CC to author]
>
> Chris Pickett <chris.pickett@mail.mcgill.ca> writes:
> > 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
>
> Try the package "ctypes.el". It does exactly what you ask. I found a
> copy here:
>
> http://www.emacswiki.org/elisp/ctypes.el
I found a more recent version here:
http://www.juliocastillo.com/emacs/site-lisp/ctypes.el
Matt
--
Matthew Kennedy
next prev parent reply other threads:[~2003-03-19 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3348.1048030940.21513.help-gnu-emacs@gnu.org>
2003-03-19 14:32 ` custom C highlighting / syntax coloring Javier Oviedo
2003-03-19 14:58 ` Peter Boettcher
2003-03-19 16:19 ` Matthew Kennedy [this message]
2003-03-18 23:42 Chris Pickett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8765qfcoqo.fsf@killr.ath.cx \
--to=mbkennedy@austin.rr.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).