From: "Javier Oviedo" <email_joviedo@yahoo.com>
Subject: Re: fontlock and imenu problems
Date: Wed, 19 Feb 2003 11:10:09 -0500 [thread overview]
Message-ID: <b30a6n$7ph$1@tilde.itg.ti.com> (raw)
In-Reply-To: m3u1f6qxgo.fsf@cicero.benny.turtle-trading.net
Thanks. How can I represent one or more spaces in the format that
c-font-lock-keywords would understand? Thanks.
"Benjamin Riefenstahl" <Benjamin.Riefenstahl@epost.de> wrote in message
news:m3u1f6qxgo.fsf@cicero.benny.turtle-trading.net...
> Hi Javier,
>
> "Javier Oviedo" <email_joviedo@yahoo.com> writes:
>
> > Is there any way around this for me? I cannot change the code since
> > I am not owner of it.
>
> Have a look at c-font-lock-keywords to see how the current scheme is
> setup and use font-lock-add-keywords to add modified versions of
> expressions that match the preprocessor commands.
>
> so long, benny
next prev parent reply other threads:[~2003-02-19 16:10 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
2003-02-13 21:39 ` Javier Oviedo
2003-02-14 23:00 ` Benjamin Riefenstahl
2003-02-19 16:10 ` Javier Oviedo [this message]
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='b30a6n$7ph$1@tilde.itg.ti.com' \
--to=email_joviedo@yahoo.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).