#!Lineno prevents syntax highlighting

[John C. Femiani]

This code:

{{{
#!Lineno
#!cpp

//Comments...
int main(int ac, char** av) {
   return 0;
}

}}}

produces this result:

Whereas this code:

{{{
#!cpp

//Comments...
int main(int ac, char** av) {
   return 0;
}

}}}

Produces this output:

I think that LineNo is supposed to use the syntax highlighting processor that follows it, as it does in the example.

--John

[John C. Femiani]

Incorrect Resuylts

[John C. Femiani]

Syntax Coloring works in my setup without LineNo....

[xyanipheia]

Unfortunately, I have the same problem.

• my installation: WinXP, Apache 2.2.11, Python 2.5.4, Trac 0.11.2.1,
• used LinenoMacro: revision 3450
• further plugins: enscript-1.6.3-9, pygments-1.0, silvercity-0.9.7 and docutils0.5, all for python 2.5.
  • These are needed by some of my colleagues fore some languages. Maybe thats the reason?
• Additionally we have installed the TracMath plugin, that also adds a syntax highlighter

Anyway, at least for simple text this macro is very usefull.

As I have installes TRAC 0.11 i change the Trac Release. I suppose, there are some dependancies to the other syntax highlighters and their priorities?

[anonymous]

Ditto - syntax highlighting does not work by itself either, so perhaps you are presuming a prerequisite component that not everyone has?

Still does a nice job as plain text.

[buaa.byl]

Replying to john.femiani@asu.edu:

[...]

If you are in windows, this may happen, I modify source to fix it. See #8329.

[Ryan J Ollos]

(In [11940])

Fixes #3680, #8329:

• Use regular expression from trac 0.11's trac.wiki.parser to match the processor type. This should fix incompatibility problems on Windows.
• Organized imports.
• Deleted empty 0.9 directory.