Arrow keys not always working Windows 10 cmd

[cveld]

When I use yo from Windows 10 cmd, the arrow keys are not always working. It then sticks into some kind of readline history list. This is not always happening. Unfortunately I can't pinpoint what is causing it. Using yo version 1.4.8.

[SBoudrias]

This is reported on the Node repo nodejs/node#2996

We're waiting for resolution on their side.

[fvilers]

Don't forget that you can select menu items by their index (one based).

[SBoudrias]

From the node bug, it looks like no keypress events at all are working on windows.

[cveld]

That is not true as most of the time I am perfectly able to walk through
the menus with the arrow keys. Somehow it gets stuck sometimes in some
floating input line itself and then all keypresses are flowing into this
floating input line instead of the registered event handlers.

2015-09-24 19:41 GMT+02:00 Simon Boudrias [email protected]:

From the node bug, it looks like no keypress events at all are working on
windows.

—
Reply to this email directly or view it on GitHub
#360 (comment).

[SBoudrias]

I meant, sometime windows just don't register them, and when that happen you don't receive any keypress event. The issue though is not always happening as sometime the keypress events are correctly fired.

[aysenz]

I using "git bash" and i have the same problem. But in Windows Command Prompt works very well.

[SBoudrias]

That have been fixed and shipped on Node.js side. nodejs/node#2996

[Schandlich]

@SBoudrias Still appears to be broken.
Will not work for me on Node 5.8 and Yeoman 1.7
Can we reopen please? nodejs/node#5384

[SBoudrias]

@Schandlich see the issue I just posted please. nodejs/node#2996

[Schandlich]

@SBoudrias Thank you. That is where I found the link to nodejs/node#5384. :D

[AmirGilboa]

still broken here. :(

[csjcode]

It's broken for me in Git Bash, but seems to work in cmd.exe

$ npm -v
3.3.12

$ node -v
v5.5.0

yo --version
1.7.0

[edgolub]

I'll just post a screenshot to express my feels:

And yes, same issue here. Win 10, node and npm versions in screenshot.

[dsouzadyn]

The issue has something to do with a recent windows update I think. It wasn't there few days ago.

[joelmez4]

I have the same issue, there is someone who already solved it?

[SBoudrias]

@nyxjoel access the generator through the yo menu. The arrow bug is a regression in Node.js, they need to fix it on their side :(

[RonAlmog]

and they did. get the latest node, npm, and yo. at least in my case, it's been fixed.

[KammererTob]

Note: It is fixed in version >= 6.2.0.
Not for 4.4.5, which they recommend for most users.

[ghost]

Still having this issue in Git Bash on Windows 10

[alegadpen]

Yep, issue still exists in Git Bash on Win10
I was able to bypass it one day, by setting some xterm function, sadfully I've lost it and now there's no way to make it work on Git Bash.

[mischah]

Reported as spam.

[dean0bambin0]

Has there been any fix for this?? Still happening for me on git bash windows 10

[SBoudrias]

Git Bash is not a TTY command line tool. As such, it doesn't support any interactive features.

You can use cmd, powershell, and a lot of other command line tool on Windows. Just make sure it is a TTY.

[dean0bambin0]

Ok Thanks, that's frustrating cause it works with git version 1.9.5.msysgit.0.

[prubini87]

Can this issue be reopened? I'm unable to use Yeoman in Windows 10.

$ yo --version
2.0.0

$ node -v
v8.1.0

Both Powershell and Command Prompt don't let me get past choosing options in the first menu. I can actually switch between them, but once I hit enter, it asks for a name for my project and then, when i type, nothing shows up, it's like it's not captuing my keyboard input...

I read some of the messages above and I decided to try git bash, which showed a slightly different behavior, but ultimately also didn't get me through the first stages much less create the source code!

[CamiloTerevinto]

Exactly the same issue as @prubini87:

windows 10
npm -v => 5.0.3
node -v => v.8.1.0
yo --version => 2.0.0

I can select the first option using arrow keys, then 100% of the input is ignored.
How can this be treated as solved if people is still getting this issue?

[SBoudrias]

@prubini87 @CamiloTerevinto looks like Node 8 broke the readline module again. You should report your issues there.

[prubini87]

@SBoudrias Yep, you may be right sir, I've rolled back to Node 6 and it's working just fine. It seems to be related to Node 8 indeed. Could you provide @CamiloTerevinto and I a link where we should report this, please?

[SBoudrias]

Bug was reported to Node nodejs/node#13557 you can follow that issue to be notified once resolved.