-
Notifications
You must be signed in to change notification settings - Fork 53
How to make it work with RVM #98
Comments
You will need to create a rvm wrapper script and set that to the executable path in Atom. |
Thanks! However, now I'm getting the following error:
The wrapper script itself is working fine, I can use rubocop without |
@andyentity you may have a better time installing it to your system ruby, it should be on your PATH so you shouldn't need to do any configuration and you won't have to remember the syntax for regenerating the wrapper script every time you update rubocop @Arcanemagus what do you think about doing something like injecting the project folder path into the configuration variable and then using binstubs? Example: I'm asking mostly because I tend to have multiple projects that run with multiple versions of rubocop (some of which are out of my direct control) and this might be a smarter way to tackle this problem. Is that a crazy idea? |
@andyentity You'll need to upgrade rubocop. The version you're using isn't supported. |
@whoward Are you talking about something like what linter-pylint does? |
@Arcanemagus i don't use that one but from the docs yeah the |
The wrapper script is competely sufficient for my needs. |
@whoward If you could file an issue to track implementing that, that would be great 😉. @andyentity glad to hear it 😄. (Marked invalid as this was a configuration issue, not a bug in linter-rubocop.) |
@Arcanemagus no problem - see #100 |
Using 000-project-shell-env you don't need to specify a path. You can just use linter-rubocop defaults. |
I provided the full correct path to rubocop in the configuration and now I am getting the following error:
This is probably because I am using RVM. If I want to use ruby in the shell,
source ~/.rvm/scripts/rvm
has to be evaluated first. The script is setting all the environment variables and stuff that are needed for the shell to find everything.How can I tell linter-rubocop (or Atom) to do this?
The text was updated successfully, but these errors were encountered: