Modify

Opened 9 years ago

Closed 5 years ago

#3680 closed defect (fixed)

#!Lineno prevents syntax highlighting

Reported by: John C. Femiani Owned by: Adamansky Anton
Priority: normal Component: LinenoMacro
Severity: normal Keywords:
Cc: John C. Femiani Trac Release: 0.11

Description

This code:

{{{
#!Lineno
#!cpp

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

}}}

produces this result:

Incorrect Resuylts

Whereas this code:

{{{
#!cpp

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

}}}

Produces this output:

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

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

--John

Attachments (2)

LineNoProblem.png (5.2 KB) - added by John C. Femiani 9 years ago.
Incorrect Resuylts
CppCorrect.png (1.4 KB) - added by John C. Femiani 9 years ago.
Syntax Coloring works in my setup without LineNo.…

Download all attachments as: .zip

Change History (6)

Changed 9 years ago by John C. Femiani

Attachment: LineNoProblem.png added

Incorrect Resuylts

Changed 9 years ago by John C. Femiani

Attachment: CppCorrect.png added

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

comment:1 Changed 8 years ago by xyanipheia

Trac Release: 0.100.11

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?

comment:2 Changed 8 years ago by 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.

comment:3 in reply to:  description Changed 6 years ago by buaa.byl

Cc: John C. Femiani added; anonymous removed

Replying to john.femiani@asu.edu:

[...]

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

comment:4 Changed 5 years ago by Ryan J Ollos

Resolution: fixed
Status: newclosed

(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.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Adamansky Anton.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.