search

workshopper / org

Organizing the workshopper environment.
9 stars 4 forks source link

Menu's not working on windows 10. #18

Open jessevdp opened 7 years ago

jessevdp commented 7 years ago

Unable to use the interactive menu to select a workshop inside any workshopper. (I've tried learnyounode and expressworks so far.) I've tested out a couple of node versions but all give the same result.

Fix (kind of)

The workshops have a command called select. Run <workshopper> select <workshop> to get to the desired workshop.

For example:

learnyounode select HELLO WORLD

Conclusion

Although there is a 'solution' to the problem this solution is not optimal. Maybe the menu's should be fixed somehow? If the fix is already out there let me know!

Cheers 👍

martinheidegger commented 7 years ago

@skillzzjesse

Thank you for reporting this problem. It would be important to know in what Terminal software (incl. version) you are using. Common Terminal Software is the PowerShell, Command Prompt , Cygwin Bash or Node.js Command Prompt.

(cc. @llkats - this is the kind of issue that I have mentioned in #13)

jessevdp commented 7 years ago

Ehm. I'm using the command prompt built into Windows 10. Running bash on startup.

I had the same issues when running on Bash on Linux on Windows. (yes that's an actual thing now... 😂)

martinheidegger commented 7 years ago

Can you give me the exact Windows Build number and a screenshot of the setup?

jessevdp commented 7 years ago

Hopefully this is helpful 😄

2016-10-21 2

2016-10-21

martinheidegger commented 7 years ago

Thank You @skillzzjesse I will keep you up-to-date once we know more. cc: @rvagg Can the Node.js team do something here?

jessevdp commented 7 years ago

Awesome! Thanks! @martinheidegger

rvagg commented 7 years ago

So @skillzzjesse since you have the Linux subsystem installed you're presumably using a developer preview version of Windows?

Do you have any special language settings other than a typical en_US or en_GB setup going on in your Windows setup? Is there anything particularly novel about your setup you can think of that might even remotely be relevant to this issue?

I'd like to hear if anyone else can replicate this problem.

You could try using Node v6 now that it's LTS or even Node v7 if you're keen but there shouldn't be anything appreciably different between those two versions so v6 is a safe bet. If that works for you at all then it'd be great to know so we might be able to narrow down the cause on our end.

wrt the Linux subsystem on Windows, don't bother at this stage, it's too raw and doesn't support some important APIs that Node needs for even basic functioning.

JoeDoyle23 commented 7 years ago

If you are using the version in the Anniversary Update (14393.351 reported by winver.exe), you have to remember its still beta with lots of stuff missing. From the GitHub repo (https://github.com/Microsoft/BashOnWindows) it looks like the next update will come around March, which may solve this.

I was able to replicate this. I did notice that you can use the J and K keys to move down and up respectively. So while not perfect, it does get you going again without specifying the step on the command line.