Geek Answers Handbook

Rbenv constantly creates a wandering gasket

I use the latest tramp with rbenv and various rubies.

I use the last stroller who no longer uses the gem. When I execute a stray command, I see the following error:

rbenv: vagrant: command not found

I removed the old stray stone from all the ruby ​​surroundings, but every time I “cd” the stray gasket is restored, which means that the stroller stops working until I adjust the gasket manually:

 rm /home/{user}/.rbenv/shims/vagrant

Is there a way to get rbenv to stop this behavior?

rbenv plugins in use ":

  • ruby build
  • rbenv-gemset
+7
source share
3 answers

Until this problem is resolved in rbenv, you can do this:

 alias vagrant /full/path/to/vagrant

Then, each time you run the tramp, the actual stray binary will be executed, not the gasket.

+5
source

Try:

ls ~/.rbenv/versions/*/bin | grep 'vagrant'

and if there is a gemset plugin

ls ~/.rbenv/*/gemsets/*/bin/ | grep 'vagrant'

If the commands return results, delete the files. After this run, rbenv rehash .

+2
source

Other people obviously had the same problem; see https://github.com/sstephenson/rbenv/issues/388 .

If you use a plug-in for rbenv, then selling a project that uses a stray stone will obviously force you to build a gasket; try removing the bundler plugin, remove the firewall pad and run rbenv rehash to fix the problem.

If you are not using the bundler plugin, can you provide us with a list of all the rbenv plugins that you use?

+2
source

More articles:


All Articles