Closed magynhard closed 2 weeks ago
Messy issue.
All the affected Rubies are EOL. Also, they report ASCII-8BIT
to the following, but Ruby 3.0 and later report UTF-8
:
ruby -e "puts ENV['PATH'].encoding"
See https://github.com/ruby/ruby/pull/3818
ridk
could be patched to work around these issues, but that still leaves issues with Ruby itself...
@MSP-Greg thank you very much for your response!
I noticed this problem because I am currently developing a version manager for the classic Windows Command Line that is compatible with RVM.io.
Since special characters in the path are probably a special Edge case as long as you do not install in the user directory, I will check to generally switch to C:\ProgramData
by default, making it even more easier to reuse it for multi user environments.
So i guess, it is not worth to make a patch for this, but to mention this problem in the docs benath the problem with empty spaces in paths, to avoid using paths with special characters: PullRequest: https://github.com/oneclick/rubyinstaller2/pull/381
There will be no further ruby-3.0.x release since it is EOL. And with #381 merged I think we can close this issue.
What problems are you experiencing?
When running ridk with Ruby <= 3.0.x from a path, including special characters (e.g. Umlauts), the ridk script crashes instantly.
Steps to reproduce
Install any ruby version <= 3.0.x from Rubyinstaller inside a path with special character, ensure PATH variable to its
bin
directory is set or open the bin directory in the command line. In my case they were installed in the user directory with a username containing a special character.Running latest Windows 11, German locale.
Then run:
The output will be:
What's the output from
ridk version
?Does not run as well, the output in this case is excactly the same as mentioned above. No ridk command is working at all. I tried the latest Ruby 2.7.8 and 3.0.7 from RubyInstaller without any modification.
Additional info
From Ruby >= 3.1.x it works without any problems, if there is a special character in the path of the ruby installation.
On Ruby 2.4.10 / 2.5.9 / 2.6.10 the error is different, here the path itself is encoded the wrong way when running
ridk
: