New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jruby-complete cannot start irb in windows #7547
Comments
It has been a while since I looked at Windows support, but I thought we had a basic win32api. Perhaps it got lost during recent version updates. |
This seems to only be an issue with jruby-complete. Seemingly we are not including win32api? Not really sure how that would have changed from 9.3 but the codebases are pretty far apart now. Confirmed locally for me at least 😄 |
Both 9.3 and 9.4 jruby-complete have the file but it is named Win32API.rb. I wonder if we did something to case insensitivity/encoding/fs where require 'win32api' will not find Win32API.rb. |
Ok. Significant difference has been found. 9.4 of complete contains reline but 9.3 does not. As mentioned before there is a file 'Win32API.rb'. Both files have it but only one is calling it during irb (9.4). Case closed? There is a mystery. If I run irb with an installation of 9.4 it starts up. Why? Is the full install loading readline capabilities different in some way between an install and jruby-complete? I did poke around enough to see I am going to rebundle jruby-complete with changed win32api.rb and see if things work but I don't feel this is good enough. Someone make this make sense :) |
renaming it does work fwiw. I still don't get why it works on a full install of 9.4 with the mixed-case name. |
I was wrong about require "Win32API". It will work on in an ordinary install but not from a file loaded via classloading (which is case-sensitive). 9.3 and earlier worked because we were not yet using reline so it was not requiring this file. Fixed in e9d8a73. |
Environment Information
Provide at least:
uname -a
)uname on windows? :)
Expected Behavior
IRB should work.
Actual Behavior
The text was updated successfully, but these errors were encountered: