From: Fang lun gang <no@mail.com>
Subject: Re: hightlight if/ifdef blocks
Date: Fri, 03 Nov 2006 20:20:41 +0800 [thread overview]
Message-ID: <87k62cg1ra.fsf@mail.com> (raw)
In-Reply-To: 1162455753.364675.44070@m7g2000cwm.googlegroups.com
>>>>> "Martin" == Martin <m.gercke@gmail.com> writes:
Martin> might or might not work with the one or the other compiler. To
Martin> avoid this uncertainty I should use #if 0 which I think makes sense
Martin> and is ok for me. (can't find the post though, sorry ...) However,
Martin> emacs does not show me these blocks as "unused" comments, but as
Martin> c-code. So, back to my original question ... how to get these
Martin> blocks to change their color :-)
Thanks at first.
As to your original question, I known there is a hide-ifdef-mode although it
may not satisfy you.
--
Fang lun gang
next prev parent reply other threads:[~2006-11-03 12:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 8:24 hightlight if/ifdef blocks Martin
2006-10-31 12:37 ` Fang lun gang
2006-11-01 1:31 ` Michaël Cadilhac
[not found] ` <mailman.3.1162344693.2155.help-gnu-emacs@gnu.org>
2006-11-01 15:05 ` Fang lun gang
2006-11-02 8:22 ` Martin
2006-11-03 12:20 ` Fang lun gang [this message]
2006-11-05 11:01 ` Martin
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=87k62cg1ra.fsf@mail.com \
--to=no@mail.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).