-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using rvm with custom gemset causes a rubocop LoadError message #19
Comments
Indeed, that seems to be a bug - using a custom gemset with rvm is currently not working. |
@Nemtes and @MatthewRDodds why simply not use bundler instead of rvm gemsets? They are redundant and bundler is better in many ways. |
+1, same issue here |
I seems to work well with custom gemset and rvm on my side out of box. |
+1, same issue |
+1 |
Rubocop package working fine for me... Including full project check. My RVM Version
Create gemset files.
Alter your gemfile to look something like this:source 'https://rubygems.org'
gem 'rubocop' Enter directory, which will generate rvm wrappers and install rubocop gem.
Rubocop packageProceed to install the rubocop package into sublime using something like Once package is installed quit all sublime windows, proceed to produce a rb file and it should be markedup by rubocop on save... |
Did you guys tried to tune config? |
same error on Linux 👍 |
The title was a bit too general, so I changed it to reflect the real initial topic. |
I know this is old but the solution for me was to install rubocop into the global gems rather than custom one. Then it worked fine, even without restarting. |
+1 |
Fix: Installed rubocop globally.
|
@karuppasamy Thank you very much for the suggestion. Installing the gem globally works for me. Have a nice day. |
If you use RuboCop with Rails, just edit or create new file .ruby-version with content like this: ruby-version@your-gemset-name. It's worked for me :) |
I am running OSX 10.9.2, with rubocop and rvm. I use a custom gemset for the project but I only can check one file and not the whole project.
The text was updated successfully, but these errors were encountered: