This is a quick one, but I'm so happy right now, I need to write this down to have it saved for future reference.
Update: Well, uhm, turned out it didn't work as well as I thought it would eventually. I'm currently working on setting up my main work laptop from scratch, and I'm switching to asdf for managing my Ruby runtimes. So far, it looks promising.
For the longest time I've failed to properly set up vscode with the ruby extension in a way that made things like linting with RuboCop work consistently.
RuboCop linting in vscode always ever worked for me when opening up vscode from a terminal (i.e. running
code . from a project's directory), which was maddening.
I just couldn't figure out why it wouldn't work otherwise. It was clearly an issue with vscode not able to find the right rubocop binary, but I just couldn't fix it and didn't find a solution to make it work with my rbenv setup consistently.
Until just now. Muahahaahaa. 🎉
Customizing what command the vscode ruby extension tries to run when it needs to fire up rubocop did the trick. I tried that before, but I couldn't figure out the right setting before. Not sure why, in hindsight it's rather obvious.
Here's what I've in my settings.json now:
command. It tells the ruby extension to use
/Users/wr/.rbenv/shims/rubocop to execute rubocop, which will do some rbenv magic to find the right rubocop executable for your current project.
/Users/wr/.rbenvis my rbenv root, obviously. You can find out where your's is by running
rbenv rootin your terminal.
I'm still not able to use the ruby extension's "format" feature, because it seems like you can't customize the command it runs. It's hardcoded to the default