Skip to content
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

Warning "io/console not supported; tty will not be manipulated" occurs again on 9.0.4.0 (2.2.2) 2015-11-12 #3700

Closed
tukanos opened this issue Feb 26, 2016 · 3 comments

Comments

@tukanos
Copy link

tukanos commented Feb 26, 2016

I'm trying to work with readline and I get this working

jruby -v -rreadline -e "p Readline.readline"

Environment

The versions installed:

--> jruby -v
jruby 9.0.4.0 (2.2.2) 2015-11-12 b9fb7aa Java HotSpot(TM) Client VM 25.66-b17 on
 1.8.0_66-b17 +jit [Windows 7-x86]
--> java -version
java version "1.8.0_66"
Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
Java HotSpot(TM) Client VM (build 25.66-b17, mixed mode, sharing)
--> wmic OS get Caption,CSDVersion,OSArchitecture,Version
Caption                         CSDVersion      OSArchitecture  Version
Microsoft Windows 7 Enterprise  Service Pack 1  64-bit          6.1.7601

Expected Behavior

To move the cursor right/left to edit output with keys right and left (gives OK output) only and not to show warning message.
io/console not supported; tty will not be manipulated

Actual Behavior

Showing the message and unable to move the caret around.

@kares
Copy link
Member

kares commented Feb 26, 2016

it has been fixed since 9.0.4.0 ... actually 9.0.5.0 should have the fix already.

@kares kares closed this as completed Feb 26, 2016
@kares kares added this to the Invalid or Duplicate milestone Feb 26, 2016
@tukanos
Copy link
Author

tukanos commented Feb 29, 2016

Not true. The issue remains still at 9.0.5.0 (I have opened separate ticket at #3704). Could you point me to the patch that should fix that?

@enebo
Copy link
Member

enebo commented Feb 29, 2016

@kares @tukanos The fix for 9.0.5.0 was to re-add a $VERBOSE check since this warning is only supposed to print out if verbose output is enabled. I explained in #3704 why this warning is being seen and opened #3705 to track implementing proper io/console support on windows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants