fontlock and imenu problems

fontlock and imenu problems

[Javier Oviedo]

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?

2. In Imenu, if a function does not begin in column zero, then imenu does
not "see" it. Again, I am forced to browse other peoples code. Any help?

Thanks in advance.

Javier

Re: fontlock and imenu problems

[David Kastrup]

"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

Re: fontlock and imenu problems

[Javier Oviedo]

Is there any way around this for me? I cannot change the code since I am not
owner of it.

Thanks.
"David Kastrup" <dak@gnu.org> wrote in message
news:x5of5fvrdk.fsf@lola.goethe.zz...
> "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

Re: fontlock and imenu problems

[Benjamin Riefenstahl]

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

Re: fontlock and imenu problems

[Javier Oviedo]

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

Re: fontlock and imenu problems

[Kai Großjohann]

"Javier Oviedo" <email_joviedo@yahoo.com> writes:

> Thanks. How can I represent one or more spaces in the format that
> c-font-lock-keywords would understand? Thanks.

I don't understand the question.  (re-search-forward "a b") is a Lisp
expression which searches for a, followed by space, followed by b.
Does this answer your question?
-- 
A turnip curses Elvis

Re: fontlock and imenu problems

[Benjamin Riefenstahl]

Hi Javier,


"Javier Oviedo" <email_joviedo@yahoo.com> writes:
> Thanks. How can I represent one or more spaces in the format that
> c-font-lock-keywords would understand? Thanks.

c-font-lock-keywords uses regular expressions (regexps for short).  If
you don't know how regexps work, get some tutorial, e.g. any
beginner's Unix intro should have a section on them.  Or you can just
jump right in and read the Emacs regexp docs at

  C-h i g (emacs)regexps RET


Hope this helps, benny