On 5 Apr 2005, at 15:54, Allan Odgaard wrote:
On Apr 5, 2005, at 16:32, Jeroen van der Ham wrote:
The reason this happens is that all the list of keywords in the syntax file are surrounded by "word seperator" matches ("\<" and "\>"). If you remove them, or perhaps just the one matching end of word, then it would match "keyword{" properly.
No, since “{” is a non-word character, this shouldn't be the problem. I'll take a look at the syntax file later today when I also change the SQL stuff.
Yes, Allan, you are correct as usual, as Jeroen's suggestion does not solve the problems. Mind you, even with my 'bug' I have separate .className, #idName, htmlKeyword and :psuedo-class highlighting that is not in the standard CSS. (just checked and re-read the comments in there ;) ) As I see it, this whole thing will work better after b6 (or later) anyway, so I'm not too bothered. It works and if it enforces a better coding style by the user then that's a good thing in my book.
Oh, and Mats, really nice work you're doing with the HTML stuff! I don't do much HTML myself, so it's nice with these “best practices” snippets that include the arguments that really should be there :)
Thanks, and if I have the time, energy and some help, you've only seen the tip of the iceberg so far. I would love to have complete XHTML code blocks, CSS styles, browser (= Win IE) workarounds etc. etc. as ready snippets. Not to mention JS scripts ready to go. "Want a style-switcher? Here you are.." type of thing
Did anyone notice my subtle drumming on about the "help" bit ? ;-)
Kind regards,
Mats
---- "TextMate, coding with an incredible sense of joy and ease" - www.macromates.com -