hlissner / doom-emacs Public
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
Windows Terminal intercepts some ctrl key sequences #2973
Comments
|
Even though it might have to do with keyboard/mappings, I tried the US keyboard and any combination of keyboard-shortcuts present in the org-mode keys. |
|
I'm afraid I can't look into this, as I don't have a Windows system handy, and know little about WSL. That said, you mention Unix terminals tend to be particular about how they translate certain key codes (sometimes ignoring certain combinations altogether), so I suspect that may be the case here as well. I don't know anything about Windows terminals, so I can't offer any insight on how to fix the issue. At the very least, I don't think this is a Doom (or even an Emacs) issue. |
|
Hey @herop, I'm a fairly new user to Emacs in general but I've just recently set it up on my desktop, which uses WSL 2. I also happen to use the new Windows Terminal so I did some testing and I think I've found some answers for you. For starters, Windows Terminal itself has some hidden keybindings which can be quite annoying. You won't find them in the user configurable JSON (under Settings in the dropdown) but you can see them here: https://github.com/microsoft/terminal/blob/master/src/cascadia/TerminalApp/defaults.json#L333 You mentioned that Assuming that I'm reading Once again, another quirk for Windows Terminal, argh. Check out this comment here: microsoft/terminal#3079 (comment) It seems that Windows Terminal treats I came up with a little test to validate this. Within org mode, Typing Typing Typing Hopefully this is enough to convince you to try out Emacs using a display server rather than the Windows Terminal, since it seems like a much nicer experience. Similarly, @hlissner I hope this post means you can remove one more bug off of your list of things to do. I'll see if I can contribute something to that missing WSL 2 portion of the install docs now as well, seeing that I now know a little bit more than last week. |
|
If I'm the only one complaining you could close the issue. I no longer care. |
|
In that case I'll consider the issue external and close this. @marcus-crane Thank you so much for looking into this and sheding light on it with such a detailed bug report! It is much appreciated. |
What did you expect to happen?
That I can do as expected:
C-c c-^-> nothing happensC-c c-<->C-c c-\is undefindedC-c c->-> nothing happensC-c c-_-> text on my screen becomes smallerWhat actually happened?
See above.
I wonder, if this only stems from my use of WSL - BUT:
^only occur if aSPCis pressed afterwards<just wont function together withC-and at leaset the>key HAS to see aSHIFTtogether pressedAdditional details:
Include a link to your private config
I'l happily obey if necessary, but we are in a different ballpark here, I assume.
Include screenshots/casts of your issue


If you mention key sequences, include what commands they're bound to (use
SPC h k KEYorC-h h k KEYto inspect keys).Include any warnings or errors logged to *Messages* (use
M-x view-echo-area-messagesto see it).Steps to reproduce:
System information:
Windows10 Insider Build Fast
WSL Debian on Terminal Preview (Insider, installed yesterday.
The text was updated successfully, but these errors were encountered: