Claudio Bley

Hi. Have a look here - https://bugs.ruby-lang.org/issues/10300 and here https://stackoverflow.com/questions/53891910/gem-install-jekyll-failure HTH

BTW, U+00AE is the character ® which you seem to have used somewhere in your msys paths. Look into the registry under `HKEY_CURRENT_USER/SOFTWARE/Microsoft/Windows/CurrentVersion/Uninstall/`. It should help starting ruby with `-E...

Hi. Thanks for the report! I am afraid, combining git status and tree is not really supported currently. It was broken before, but my last changes made it worse since...

Hi. What happens when you run `RUBYOPT=-Ku colorls d:/` instead?

I found this bug report which might be related: https://bugs.ruby-lang.org/issues/14591 What is the output of `ruby -e 'puts Encoding.find("filesystem")'` on your machine? And what filesystem is on D:\? NTFS?

> ruby -e 'puts Encoding.find("filesystem")' > Windows-1251 I guess that's bad. As you cannot properly encode chinese characters with CP 1251. That's probably why you only see those question marks...

Did you try with `-Ku` as before?

You could also try `set RUBY_DEBUG=codepage=65001`.

FTR, here is how Ruby initializes the encoding it uses for filesystem operations on Windows: https://github.com/ruby/ruby/blob/c5eb24349a4535948514fe765c3ddb0628d81004/localeinit.c#L124-L130 To make it work, you need to use a codepage which properly encodes all...

After lots of back-and-forth (https://github.com/avdv/clocale/pull/45/commits), I discovered that `Dir.entries` accepts an `encoding` parameter since Ruby 2.1. That way, I can force the Encoding to be UTF-8, which seems to work:...