Sublime Text has been my go to editor since John De Goes introduced me to it around 2010, during our time at SocialMedia.com. I had already been looking for a new cross-platform editor to replace my beloved jEdit, which even then was feeling a bit old and neglected. It took a year or so before I was able to fully make the switch (Sublime Text was in pretty heavy development at the time), but these days, you can find a plugin to help with just about anything.
Once it’s installed, type
ctrl+shift+p (Win, Linux) or
cmd+shift+p (OS X) followed by
package (all Package Control commands begin with “Package Control:”).
- SublimeLinter-annotations (marks annotations such as
- SublimeLinter-rubocop (runs RuboCop on your Ruby code as you’re editing it)
These plugins have saved me from countless errors.
GitGutter shows you what lines were changed, added, or removed since your last commit. It’s like having a constantly updated
git diff built in to your editor.
There’s nothing worse than updating a
README.md and not realizing that your formatting is all screwed up until you look at it on GitHub. The MarkdownEditing plugin gives you some nice Markdown syntax highlighting, so you can preview your changes before committing them. Like the SublimeLinter plugins above, this one has saved me from countless errors.
The context menus in Sublime Text’s sidebar are pretty limited by default. The SideBarEnhancements plugin adds lots of useful file operations.
The Chef plugin hasn’t been updated in a long time, but it’s still useful in Sublime Text 3. It provides auto-completions for most of Chef’s built-in resources, which makes writing cookbooks faster and easier.