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

Generator doesn't respond to arrow keys in Windows 10 #8

Closed
xabikos opened this issue Nov 8, 2015 · 9 comments
Closed

Generator doesn't respond to arrow keys in Windows 10 #8

xabikos opened this issue Nov 8, 2015 · 9 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@xabikos
Copy link

xabikos commented Nov 8, 2015

I installed the latest version of the generator as pointed in here. After doing that the generator launches normally but I can't navigate among the various options with the arrow keys. This happens on Windows 10 environment. I don't know if it's relevant but the same happens to the asp.net yeoman generator. In OS X environment everything works file.

@seanmcbreen
Copy link

We have seen this issue where users are not on the latest latest version of node - do you want to give that a try?

@egamma
Copy link
Member

egamma commented Nov 8, 2015

A work around that has worked for me was to start with 'yo' and then navigate to the 'code' generator. This instead of using 'yo code' or 'yo aspnet' directly.

@xabikos
Copy link
Author

xabikos commented Nov 8, 2015

This is my configuration. I think I have latest node and npm.

config

In any case I did what @egamma suggested and was able to bypass the problem. We should probably close this issue.

@billti
Copy link
Member

billti commented Nov 18, 2015

The root cause appears to be in Node v4+ (and currently still open).

OmniSharp/generator-aspnet#351
nodejs/node#2996 (comment)

Seems like Win10 folks may need to use Node 0.12 for now to use the Yeoman generator for extensions (or use the workaround from @egamma which also worked for me).

@bpasero bpasero added the bug Issue identified by VS Code Team member as probable bug label Nov 20, 2015
@bpasero bpasero self-assigned this Nov 20, 2015
@ilich
Copy link

ilich commented Nov 20, 2015

I am on Node 5.0.0 and Windows 10. It does not work if I run the generator using yo code command, but it works if I run yo and choose Code generator there

@wholroyd
Copy link
Contributor

wholroyd commented Jan 5, 2016

I am on Node 5.3.0 with Windows 10. I did have the issue on 4.x until I upgraded, but now no longer have the issue.

@bpasero
Copy link
Member

bpasero commented Jan 5, 2016

Thanks!

@bpasero bpasero closed this as completed Jan 5, 2016
@kia-h
Copy link

kia-h commented Feb 18, 2016

if it doesn't wok in Git Bash, try powershell. just run the yo then select your generator

@bilazik
Copy link

bilazik commented Aug 25, 2016

In powershell works great. It don't works from cmd without Admin execution.
VS code integrated terminal works fine with Admin opts too.
Thanks guys

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

9 participants