I've attached a file with some system info, showing the results of some CLI commands. I seem to have mucked up my RVM install and would rather fix it then re-install to avoid recompiling ruby. The first time I installed rvm I did so as root before realizing that wasn't a good idea. Then, I installed rvm and got it mostly working, except for a dependency problem for a particular gem. So, the recomendation I got, which made sense, was to recompile ruby with that lib already installed.
At that point I did an "implode" on the user installed RVM, then realized that the root RVM was still hanging about, so imploded the root version after the user version. I think that's the cause of the current problem.
In any event, I can't get gems on to the working path. The litmus test for this problem seems to be that the command:
thufir@caladan:~$ type rvm | head -1
rvm is hashed (/home/thufir/.rvm/bin/rvm)
thufir@caladan:~$
isn't outputting the expected "rvm is a function
".
See attached bash.txt file for details, please.
I've looked at
https://rvm.beginrescueend.com/workflow/scripting/ but am unclear as to why rvm appears to running as a binary nor what's really wrong with that.
thanks,
Thufir