I continue to use and be impressed with the Atom editor from the lovely people at github. A modern text editor with a built-in packaging system to allow adding in, well, add-ins that provide cool and needed functionality. One of the new ones that I’m using a lot is git-plus.
If you keep getting popups errors in the github Atom text editor when using Rubocop then maybe its this issue I just had. While working on a gem complaining about a missing rubocop version or in general giving odd and annoying errors you should try and remove your Gemfile.lock file in the root of your gem folder and run bundle install again. It could be that the Gemfile.lock is pointing at a rubocop you no longer have installed. I was frustrated for several minutes about these errors when I brought up an older gem to test out Rubocop integration with Atom until I realized that I probably had done a bundle install way back when I wrote this gem and created the Gemfile.lock file which the Rubocop was trying to respect.
If you haven’t checked out the Atom editor from the lovely people at github then its worth your while. A full-featured and more and more popular editor with a growing set of packages that can be added in to provide some cool functionality. Since I’m doing more and more Ruby programming I wanted to install the rubocop lint functionality within the Atom editor. This is provided by the linter-rubocop Atom package. So this blog post might be interesting if you code in Ruby and are open to trying a new text editor.
I continue to try and get Atom setup in the most productive way - especially for Ruby programming. I continue to be impressed with the tool. For unit testing I favor MiniTest and I wanted a way to run tests from inside Atom without leaving the editor environment.
Lag came in handy again.