Hi,
I do like TM's syntax highlighting a lot, but I think it's annoying having to tweak their color schemes to my liking all the time. I think the parser bundles should tell TM the kind of a piece of text (comment, reserved word, string, etc) instead of font style information, and TM should give me a way to apply a custom stylesheet to all that info.
So I would like to have one file containing my custom stylesheet that tells TM to display all comments (regardless of language) in green, all strings in purple, except for perl, where I'd like my strings to be blue. You get the idea.
How does that sound?
Cheers, -Ralph.
BTW, that's the feature request I wanted to add to the wiki before I broke it..
hi,
i also would like to see it implementet this way, this also solves the problem of white on black or black on white highlights because everybody can set its own preferences.
my suggestion would be to implement this as variables in the colors of the highlights. so one can to foregroundColor = "$STRING"; or something like that.
it would be probably also a good idea to be able to set vaiables like this in the beginning (or anywere else) of a highlight file so it would be faster to adjust if something changes.
On Nov 26, 2004, at 12:50, Ralph Pöllath wrote:
I do like TM's syntax highlighting a lot, but I think it's annoying having to tweak their color schemes to my liking all the time. I think the parser bundles should tell TM the kind of a piece of text (comment, reserved word, string, etc) instead of font style information, and TM should give me a way to apply a custom stylesheet to all that info.
Already planned: http://one.textdrive.com/pipermail/textmate/2004-November/001455.html
I'm doing one or two more 1.0.2 beta versions and then I'm starting 1.1 and putting all the minor stuff on hold.
I may send a list of what 1.1 will be about or perhaps use the wiki for a more public to-do (not decided on this yet -- I don't mind an open process).
This also means that if you have something that frustrates you _a lot_ with the current versions and you think it's easy to fix, you may want to mention it -- but if it's already been mentioned a few times, chances are that it's postponed because it's not a minor thing, or it'll automatically be done in the 1.1 overhaul.
-
Allan Odgaard -
Ralph Pöllath -
Torsten Becker