OSX 10.8.3, fish 2.0 open beta r2, rvm 1.19.1

In rvm.fish, the output of env contains several lines like rvm_notify_clr=<code> where rvm stores color codes for different messages. When passed to $env_file, they are rendered as ^[[..., and when fish tries to evaluate this (sed'ed) file, the unmatched parentheses produce an error like

fish: Tokenizer error: 'Unexpected end of string, parenthesis do not match'

Probable solution would be to encode color codes so that fish would understand them, or at least strip them during the creation of $env_file. Unfortunately, I do not know about bash and fish enough to fix it myself. I tried removing color codes with sed as

sed "s/\x1B\[([0-9]{1,2}(;[0-9]{1,2})?)?[m|K]//g"

but it did not seem to work. Any ideas?

Hi!
I noticed that RVM function doesn't work under Alpine Linux due to a missing argument in the grep execution.

To make it work, simply change line 7 of file fish-nuggets/functions/rvm.fish to this:

and eval (grep -E '^rvm|^[^=]*PATH|^GEM_HOME' $env_file | grep -v '_clr=' | sed '/^[^=]*PATH/s/:/" "/g; s/^/set -xg /; s/=/ "/; s/$/" ;/; s/(//; s/)//')

Hope this helps!
Paolo

I have installed the rvm function this April. And I found that rvm would mess up my variables unrelated to Ruby installation.

Here is the simplest form of my problem:

$ set -xg GOPATH /home/foobar/foo:/home/foobar/bar
$ echo $GOPATH
/home/foobar/foo:/home/foobar/bar
$ rvm use default
Using /home/foobar/.rvm/gems/ruby-2.4.1
$ echo $GOPATH
/home/foobar/foo /home/foobar/bar

Seems rvm swaps the colon : with \x1E. Unfortunately, Golang's toolchain needs the variable in its raw form. The rvm function should not assume that all *PATH variables need to be converted to fish native array.

Also reported here: fish-shell/fish-shell#4039

See

This file is linked directly on https://rvm.io/integration/fish. As such, it should be implementation specific.

The rvm source file should be based on the existing rvm script file of ~/.rvm/scripts/rvm or /usr/local/rvm/scripts/rvm.

I followed the instructions on the RVM website for installing rvm with fish. After doing this, the cd - command, which normally changes the working directory to the previous directory I was in, no longer works. Instead I get this error:

cd: The directory '-' does not exist

Any idea why or how I can fix this?

After updating fish to version 2.3 this warning is popping up when call the first time rvm use ruby-2.3.0. Future rvm calls are working properly.

Warning! PATH is not properly set up, '/home/lho/.rvm/gems/ruby-2.3.0/bin' is not at first place,
usually this is caused by shell initialization files - check them for 'PATH=...' entries,
it might also help to re-add RVM to your dotfiles: 'rvm get stable --auto-dotfiles',
to fix temporarily in this shell session run: 'rvm use ruby-2.3.0'.

I added also set -g -x PATH $HOME/.rvm/bin $PATH to config.fish

Basically this destroys custom user supplied paths in ~/.config/fish/config.fish.
The quick fix for this is to set PATH after that eval.
Please fix this so that if looks something like that:

set PATH $rvm_paths $PATH

I'm using fish in Cygwin, so that PATH variable contains paths with "Program Files (x86)" directory. The issue is that sed invocation in 8th line of rvm function is stripping parenthesis from paths, which makes them invalid.

My quick and dirty workaround was to change this line to:

and eval (grep -E '^rvm|^PATH|^GEM_PATH|^GEM_HOME' $env_file | grep -v '_clr=' | sed '/^[^=]*PATH/s/:/" "/g; s/^/set -xg /; s/=/ "/; s/$/" ;/; s/(//; s/)//' | string replace "Program Files x86" "Program Files (x86)")

I'm not sure why you are stripping parentheses (fa28b00), but if that isn't necessary then solution would be to just don't ;) (that is, remove s/(//; s/)// part of sed script)