Difference between revisions of "Sublime - For Ruby"
m (1 revision imported) |
|||
| Line 1: | Line 1: | ||
[[Category:RubyOnRails]] | [[Category:RubyOnRails]] | ||
| + | <div style="float:right;">__TOC__</div> | ||
| + | |||
| + | == LINKS == | ||
| + | [https://mattbrictson.com/sublime-text-3-recommendations https://mattbrictson.com/sublime-text-3-recommendations] | ||
| + | |||
| + | [http://sublimecodeintel.github.io/SublimeCodeIntel/ http://sublimecodeintel.github.io/SublimeCodeIntel/] | ||
== Install Package Control == | == Install Package Control == | ||
Revision as of 12:28, 28 February 2017
LINKS
https://mattbrictson.com/sublime-text-3-recommendations
http://sublimecodeintel.github.io/SublimeCodeIntel/
Install Package Control
Install RSpec
https://github.com/SublimeText/RSpec
Another Test Stuff
https://github.com/cyphactor/sublime_guard
Install ApplySyntax
https://github.com/facelessuser/ApplySyntax
Install CTags.
CTags let you quickly navigate to code definitons (classes, methods, etc.). First:
$ brew install ctags
Then use Package Control to install the ST2 package. Check out the default CTags key bindings to see what you can do.
Running RSpec from Sublime Text 2
https://github.com/neilsarkar/sublime_user_directory/blob/master/rspec.py
With this script installed, you can bind ⌘R to run the current file and ⌘⇧R to run the current test. The tests will run in Terminal. This is great for a number of reasons:
You can use any RSpec formatter and get nice, colored output. Adding calls to debugger or binding.pry works. No need to change how you run your tests when you want to debug.
Window management. It’s smart enough to reuse the Terminal window for new test runs if you don’t close it. I put my Terminal window on the right 40% of my monitor. This has really improved my TDD workflow when working on individual classes.
More
Can be found here