hello,
first: I know, I can adjust this locally myself - but then I'd have to re-do that, everytime the XMLBundle gets updated (or - from my understanding - my modifications would overrride any future updates to the XML Bundle in which case I'd have to forego them...)
my request: pls include the following suffixes for the XML-Language:
.pt .cpt .dtml .xsl
the first three come from Zope development and AFAIK don't conflict with any other suffixes.
I'm sending this to the list, because I couldn't figure out, who 'duff' is, the user committing the most recent changes to the bundle (Brad Miller?!)
best regards and thanks,
tom
At 11:54 PM +0200 4/24/05, Tom Lazar wrote:
I'm sending this to the list, because I couldn't figure out, who 'duff' is, the user committing the most recent changes to the bundle (Brad Miller?!)
'Duff' is Allan, who used to be an actress http://www.hilaryduff.com and now programs for fun.
- Eric
On 4/24/05, Tom Lazar tom@tomster.org wrote:
my request: pls include the following suffixes for the XML-Language:
.pt .cpt .dtml .xsl
the first three come from Zope development and AFAIK don't conflict with any other suffixes.
Hi, I think your problem will be solved with one of the next betas (ist actually working in b6) there is a new way to identify a language by its first line, so if all your XML files start with a <?xml (as they should) TM will identyfy them as XML and highlight them so. This will work for any extension and will this way be better than adding support for any possible extension which could be XML. So my suggestion: wait some days/weeks :)
BTW, shouldn't TM remember it if you choose to highlight .xsl files with the XML language, I am not sure...
On Apr 24, 2005, at 11:59 PM, Eric Hsu wrote:
'Duff' is Allan, who used to be an actress <http:// www.hilaryduff.com> and now programs for fun.
all in all an excellent career move of allan!
...especially since the number of male fans shouldn't have changed all that much ;-)
tom -- Tom Lazar http://tomster.org
On Apr 25, 2005, at 8:49 PM, Torsten Becker wrote:
Hi, I think your problem will be solved with one of the next betas (ist actually working in b6) there is a new way to identify a language by its first line, so if all your XML files start with a <?xml (as they should) TM will identyfy them as XML and highlight them so. This will work for any extension and will this way be better than adding support for any possible extension which could be XML. So my suggestion: wait some days/weeks :)
I remember, that at some point it already worked this way (I was rather impressed). I'm positive it will return.
BTW, shouldn't TM remember it if you choose to highlight .xsl files with the XML language, I am not sure...
me neither... can't tell anymore, though - allan added the new extensions already to the XML.tmbundle ;-)
TextMate definitely makes my work (even) more enjoyable... again and again...
best regards,
tom
Tom Lazar http://tomster.org
On Apr 25, 2005, at 21:23, Tom Lazar wrote:
BTW, shouldn't TM remember it if you choose to highlight .xsl files with the XML language, I am not sure...
me neither... can't tell anymore, though - allan added the new extensions already to the XML.tmbundle ;-)
Beta 5 and earlier would remember when the user changes language for a given extension.
I removed that in beta 6 because it now also looks at the content, so it's not entirely clear when it makes sense to adopt the users choice. E.g. opening a CGI file and changing it to perl does not mean all CGI's should open as perl, since CGI's may often have a shebang in the top that would identify these correct.
So actually in beta 6 there is no way to override the default choices for languages (well, actually there is, but it involves hitting Terminal.app and using 'defaults') -- but I'll of course add something. I prefer when things are implicit, and just haven't found the proper way to learn from the user how document bindings should be.
On Apr 26, 2005, at 10:01 AM, Allan Odgaard wrote:
So actually in beta 6 there is no way to override the default choices for languages (well, actually there is, but it involves hitting Terminal.app and using 'defaults') -- but I'll of course add something. I prefer when things are implicit, and just haven't found the proper way to learn from the user how document bindings should be.
while this approach is a bit inconvenient at the moment for me, i fully agree with your approach. perhaps the language widget in the statusbar as a compromise is easier to implement? *nudge* *nudge*
tom
-- Tom Lazar, http://tomster.org
-
Allan Odgaard -
Eric Hsu -
Tom Lazar -
Torsten Becker