Closed stickupkid closed 12 years ago
Normally, error highlighting should work, currently. So if it's not working for you, could you please give more detail, for instance your ST2 version, but also, maybe the structure of your project. Also, error highlighting should work on Ctrl+Enter, but probably not on F7. Can you confirm you're using F7 and not Ctrl+Enter ?
Yeah sure. I've been getting the console errors, but not any visual indication in the editor (which is what I'm referring to), with cmd+b, F7 and not with ctrl+enter as this just says it's built fine which is a complete lie as I've got an error.
OS: Mac OS X 10.7.4 Build: 2181 (Beta)
Building: https://github.com/stickupkid/funk-gui
Ok, so F7 and Cmd+B are not supposed to highlight errors... Well, they kind of should, but through the ST2 build system, and it doesn't seem to understand error lines very well... It's not the "recommanded" way to compile with this bundle anyway.
As for Ctrl+Enter, it will build only one of the sub-build you have, which is, when it finds your .hxml, it will split it every "--next", and attempt to build the first "part". You can choose the build you want among these "subbuilds" with Ctrl+Shift+B. Can you confirm this works, and your first sub-build gets run, and you can change builds ? Otherwise, may I see your .hxml, and know where it is in your project directory, and how it's named ?
Regards, Clément
You are indeed correct. Closing the issue.
It would be good to somehow trigger error highlighting (I'm not 100% sure you can even show errors in Sublime?) to make it easier to see errors etc (maybe do it on building?).