Verify this is working?

[jacobeatsspam]

When I open the developer tools and check process.env, I don't see the values in my .envrc, and I see no where in your code where you are setting process.env to anything...

[jhgarner]

Although I'm not rubymaniac, I've been able to get it working well on my own machine using a fork. The dev tools don't show the path changes in process.env, but other plugins do see it. Is there something specific that isn't working?

[jacobeatsspam]

@jhgarner I don't see plugins picking them up. e.g. java doesn't use the correct maven, and python doesn't pickup the correct python, despite and adjusted PATH

[jhgarner]

That's what I was seeing before the fork I made. I think the problem was that this plugin didn't get loaded early enough and didn't block the loading of other plugins so those would load with the old path. I'd be curious to see if building/installing the pull request I have open fixes your problems. Basically, in the root of the fork, you can do "yarn install; node_modules/vsce/out/vsce package; code --install-extension vscode-direnv-0.0.2.vsix" and relaunch VSCode.