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

WSL2 is better behaved that old "bash on windows" WSL #39

Open
BlameTroi opened this issue Oct 25, 2020 · 1 comment
Open

WSL2 is better behaved that old "bash on windows" WSL #39

BlameTroi opened this issue Oct 25, 2020 · 1 comment

Comments

@BlameTroi
Copy link

Working through this with WSL2 and various terminal and keyboard related behaviors just work right now. One specific instance, chapter 5 in the save as section:

"(Note: If you’re using Bash on Windows, you will have to press Escape 3 times to get one Escape keypress to register in our program, because the read() calls in editorReadKey() that look for an escape sequence never time out.)"

Works fine with a single keypress of ESC on my configuration. Suggest changing wording about Bash on Windows to "Bash on Windows prior to WSL2" or similar. Great job on the whole thing though. Appreciated.

@SRNissen
Copy link

SRNissen commented Feb 20, 2023

Much to my chagrin - WSL2 is better behaved than my actual linux distro.

I was happily plucking away at the chapters on a windows machine, then at step 44 I switched to a linux machine, pulled down my repo, and... suddenly ctrl-q doesn't work! I have go go all the way back to step 32 to get a version of the program that will actually exit without me terminating bash (edit: though for some reason ctrl-shift-q does work)

disregard i am terrible

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

2 participants