Packages

If you find any bugs with the JavaScript syntax, definitely report them at https://github.com/sublimehq/Packages/issues. As far as I know, our syntax definition is pretty spot on with the current state of the language and I believe supports all of the stage-3 proposals in TC39 (see https://github.com/sublimehq/Packages/issues/1269 for more info). The major thing we don't support out-of-the-box right now is JSX. If you are using JSX or Flow I highly recommend https://packagecontrol.io/packages/JSCustom. It is maintained by the primary contributor to the default JavaScript syntax. With our high-quality JavaScript syntax, things like Goto Definition and Goto References should work well. I'm not sure what else you may be looking for in JS projects, but there are certainly tons of third-party packages for things like linting and so forth. Myse

If you want git support out of the box, please give me a thumbs up on this PR. https://github.com/sublimehq/Packages/pull/1126 If you can read sublime-syntax files, code review is appreciated as well. With this package, you can set Sublime to be your git editor like this: $ cat ~/.gitconfig [core] editor = subl -w ...

Thanks for the feedback! I'll talk to Jon about trying to make the website push people to the forum to see what is going on. We no longer keep compatibility with TextMate in any of the default syntaxes. Everything is now a .sublime-syntax, and has access to all of the advanced stack and scope manipulation features. If you are interested in providing feedback, the packages are at https://github.com/sublimehq/Packages. Tests could be helpful, even if failing. The test syntax is described at http://www.sublimetext.com/docs/3/syntax.html#testing and scope naming guidelines at http://www.sublimetext.com/docs/3/scope_naming.html.

I set my autocomplete/snippet expansion key to tab (it's a Sublime setting) so that I never have any conflicts. Sublime actually tries harder than other editors to avoid these, but it's not perfect. See for example https://github.com/sublimehq/Packages/blob/master/Ruby/Compl... which stops it from autocompleting on common end of line keywords in Ruby. This wasn't a default in Emacs so I had to spend a couple of hours figuring out how to do this myself before I could do newlines: https://github.com/syl20bnr/spacemacs/pull/174 I'm not sure there are any editors that have auto-complete on enter but don't have any issues with conflicts.

Packages are now on GitHub, you are free to submit a patch or report an issue: https://github.com/sublimehq/Packages/issues

If you are using the recently-added default Rust syntax for Sublime Text and run into any issues, please let me know by filing an issue at https://github.com/sublimehq/Packages/issues.

I‘ll be working on everything related to Sublime Text. I was part of the dev releases building up to 3103, moving the forum and merging in pull requests from https://github.com/sublimehq/Packages. We are definitely working on improving all the different aspects of Sublime, so you can expect to continue seeing new builds!

I can't help but think it's funny that Sublime Text uses - XML for snippets (https://github.com/sublimehq/Packages/blob/master/C%2B%2B/fo...) - YAML for syntax files (https://github.com/sublimehq/Packages/blob/master/C%2B%2B/C%...) - JSON for settings (https://github.com/sublimehq/Packages/blob/master/C%2B%2B/C%...) - and plist for TextMate compatibility (https://github.com/sublimehq/Packages/blob/master/C%2B%2B/In...) Of course each one has a reason to be that way, but it must be really annoying to maintain.