Open Fridus opened 10 years ago
A member on my team has the same issue, but it is strangely working for me...?!
This is a straight port from the old TextMate bundle, which still had bugs for cfscript support. If i had more time, I would have ported the better SublimeText bundle :(
The only problem i'm getting is that it's rendering the cfscript
tag as "cfscriptscript" (?!)
I might track down cfscript
support, but in the meantime, feel free to contribute a pull-request.
Sorry if this sounds dismissive, it is not my intention!!!
A fellow Belgian, I see ;)
@nemoDreamer :) , from ?
Is not in a <cfscript />
tag.
My file:
component {
...
}
Ah, yes… the TextMate and SublimeText bundles were never capable of supporting pure CF Script… If the extension is identical, the bundle won’t be able to tell that you want script vs. tag, sorry. The solution that the SublimeText bundle had was to allow you to load a "CFComponent Script” syntax by exception.
Oh: and I'm one of those mixed-up germanophone Belgians from Eupen, but w/ a francophone mother from Liège ;)
I use sublime text since one year And I would try atom :) So, is it possible to fix this bug ? Which you prefer? Atom? Sublime ? Textmate?
Hey thanks nemoDreamer. Also a Subllime user and write CF a fair amount. I'd like to see more complex highlighting. I'm not great with these cson files but see what I can do to contribute.
Thanks again.
Thanks, @justinwhall!
@Fridus, since the developers behind SublimeText and TextMate have gone AWOL and aren't planning to go open-source, I'd say Atom is definitely the most promising choice. It'll just take a while for packages to become mature enough...
Since I work for a company that still uses CF, I've been using the SublimeText bundle for a couple of years, and it's much better than the TexMate one. Sadly, porting from SublimeText to Atom is way more complicated... :cry:
Are there two separate issues here? I came to report a problem with the <cfscript>
tag when used in an ordinary CFM file. As @nemoDreamer described, a closing </cfscript>
tag actually appears as </cfscriptcfscript>
, and the cursor actually doesn't go past the end of what would be a "correct" closing tag. Just a visual bug. Is this what the original poster is describing, or should we raise a new issue? Dan
Sorry, folks: I'll be posting a "no longer maintained" change to the README soon, as I no longer work for a company that develops in CF. I'd only created this port so that my back-end dev colleagues could hop onto the Atom wagon...
I recommend you switch to https://github.com/atuttle/atom-language-cfml, which is actively maintained, and they have fixed this nasty bug there already!
Thanks for being active here!
Not working with cfscript
component { }
in myApplication.cfc