From: David Kastrup <dak@gnu.org>
Subject: Re: fontlock and imenu problems
Date: 13 Feb 2003 21:48:39 +0100 [thread overview]
Message-ID: <x5of5fvrdk.fsf@lola.goethe.zz> (raw)
In-Reply-To: b2guip$bbi$1@tilde.itg.ti.com
"Javier Oviedo" <email_joviedo@yahoo.com> writes:
> Hello all!
>
> 1. I am seeing that sometimes #define/#include and #ifdef/#else/etc. are not
> fontified in some c-code that I am looking at. The issue seems to occur only
> if the above do not begin in the column zero. There is some code that I must
> browse that indents these, especially the #ifdef/etc, and I'd like to see
> them fontified and usual. Any help?
There is a reason:
Preprocessing directives are recognized in traditional C only when
their leading # appears in the first column. There can be no
whitespace between the beginning of the line and the #.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2003-02-13 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 20:19 fontlock and imenu problems Javier Oviedo
2003-02-13 20:48 ` David Kastrup [this message]
2003-02-13 21:39 ` Javier Oviedo
2003-02-14 23:00 ` Benjamin Riefenstahl
2003-02-19 16:10 ` Javier Oviedo
2003-02-19 16:50 ` Kai Großjohann
2003-02-19 21:20 ` Benjamin Riefenstahl
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=x5of5fvrdk.fsf@lola.goethe.zz \
--to=dak@gnu.org \
/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).