Summary: I finally managed to get Trac to supported the haXe language.
1. I created a new lexer in for haXe by in lexers/compiled.py and
adding the lexer name to the table in lexers/_mapping.py . It is
important that the entries match the names in the new lexer precisely.
The easiest way to test that the new lexer works is by using
/usr/bin/pygmetize MyCode.hx to see that the lexer works. For the
interested, I have put a Debian package here:
http://people.debian.org:~jps/unstable .
2. The file extension "hx" was not known on my system, so I had to
add a line to /etx/mime.types:
"text/x-haxe hx"
3. Trac must be told to use Pygments instead of Enscript for the
haXe file in trac.ini:
[mimeviewer]
pygments_default_style = trac
pygments_modes = text/x-haxe:haxe:7
It seemed it was necessary to both completely purge the
python-pygments package before installing the new one and to restart
Apache before Trac would obey the new pygments.
Cheers,
--
Jens Peter Secher.
_DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
