Best IT Recipes

Warning! PATH is configured incorrectly, usually caused by shell initialization files

Whenever I go to the folder with the .rvmrc file, a warning appears:

 Warning! PATH is not properly set up, '/home/me/.rvm/gems/ruby-2.0.0-p247/bin' is not available, usually this is caused by shell initialization files - check them for 'PATH=...' entries, to fix run: 'rvm use ruby-2.0.0-p247'.

I did rvm use ruby-2.0.0-p247 , but the warning is still present.

Note : there are no errors, I can just launch the application, but the warning is very annoying. Any ideas?

+43
ruby rvm
Jul 31 '13 at 11:02
source share
8 answers

It was a mistake, and it was handled using https://github.com/wayneeseguin/rvm/issues/2050 and was released as stable rvm 1.21.15 on 2013-07-29 19: 15:30 -0700

+8
Jul 31 '13 at 14:01
source share

I received the same warning even after updating RVM to version 1.25.16. I was able to fix the warning by doing:

 rvm reset

Then when I ran:

 rvm version

I no longer got the error. Hope this helps!

+100
02 Feb '14 at 15:57
source share

If you know what you are doing, and your PATH configured for what you want, you can suppress this message by putting the following in your ~/.rvmrc :

 rvm_silence_path_mismatch_check_flag=1

This is convenient if you use other traffic management programs, such as virtualenv, or just want to prefix your path with ~/bin or something like that.

+28
Nov 13 '13 at 17:27
source share

I managed to get rid of this by doing

 rvm get head
+11
Jul 31 '13 at 13:14
source share

I had a problem too and rvm get head did not work for me, finally it was resolved by running rvm get head --auto-dotfiles and then restarting the terminal and the annoying warning message disappeared! And the solution is found here: https://github.com/wayneeseguin/rvm/issues/2074 Hope this helps.

+6
Aug 05 '13 at 3:08
source share

rvm get stable solved it for me

(as stated in comments on another AndrewMarshall answer)

+2
Dec 18 '13 at 16:58
source share

Solved!

Attention! PATH is configured incorrectly, '/home/vaibhav/.rvm/gems/ruby-2.3.1/bin' is not in the first place, it is usually caused by shell initialization files - check them for the entry "PATH = ...", it can also help re-add RVM to your dotfiles: "rvm gets stable --auto-dotfiles", to temporarily fix this shell session: "rvm use ruby-2.3.1".

 rvm get stable --auto-dotfiles

Then you can get below Error:

RVM is not a function, choosing rubies using rvm ... will not work. You need to change the terminal emulator settings to enable the input shell. Sometimes you need to use / bin / bash --login as a command.

Please visit http://www.rortuts.com/ruby/rvm-path-is-not-properly-set-up/ for an example.

0
Jan 6 '17 at 6:20
source share

Ok, so I ran the export PATH command without understanding the consequences and faced the same error, but I also lost control of my typical commands like cd and pwd. I did not want to reset the rvm tools that I already installed to some of the answers above.

The first attempt was some default path for Mac (found on google):

 $ export PATH="/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin"

Actually, I solved the first problem of not having access to my typical command line tools, but still getting the same error as the problem with @Santosh. The next thing I did was go to my directory, where I installed rvm to run, and then run a new export command as follows:

 $ export PATH="$PATH"

This is how I originally set up rvm, and no more errors. Hope this helps someone.

0
Mar 04 '17 at 19:23
source share


More articles:


All Articles