-
-
Notifications
You must be signed in to change notification settings - Fork 108
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
Modifier keys (such as AltGr-f for [
, AltGr-c for &
, etc.) not supported on Windows
#150
Comments
A few more context. I have tried the same workflow but with Turning over to Unfortunately, the only Linux machine I can get to right now is too old (Debian 10) to install the dependencies needed. (*): Sadly, I can't get used to the |
Using I've tried this out on Linux. As Ubuntu 18.04 release is still the one from the past year with too new and nonexistent dependencies wanted, what I did was to install However, on the topic of modifier sequences. Let's imagine I want to type Inside Docker, I've run the following commands, just to ensure that stuff like
I've also ran My main machine is set to the
So now typing into Bash from Konsole works: Now if I start contour, it works: So it seems if the system is set in just the right way (with all the hassle ensuring it works fine inside Docker!) then the escape sequences are respected. It also works inside |
Oh that is a really precious insight. Many thanks for your detailed comment. I am currently on the making-fonts-look-awesome-spree, and this ticket (modifier keys) is most likely the next one to tame (for a satisfaction-by-default-installation). What I wonder is, that with using Konsole it worked for you out of the box, and using contour only after your keyboard settings tweak? Maybe I am misunderstanding here? -- I'd like to provide an out-of-the-box experience, so I would want to make contour keyboard input work the same way as other major terminal emulators (at least gnome-terminal / konsole / xterm). p.s.: do I understand that correctly, your Linux host is Ubuntu 18.04? if so, I think I should not drop 18.04 support just yet but instead really make sure it works without hassles. |
Yes, that's the next comment. I've managed to hack contour up to my normal system (made a tarball, installed all the dependencies manually instead of using the release So this whole keyboard layout issue is a Windows-specific thing now. I do not have macOS to test. Yes, I am Ubuntu 18.04, and it is very unlikely to change for a few years still. (It's corporate machine, I have no control over the base distribution.) So at least as long as Ubuntu 18.04 is supported officially (until 2023 or somesuch, it's 16.04 that is expiring this April) please don't drop support. |
Okay, I'll ensure Ubuntu 18.04 then. I am also very happy that your special font symbols (left side of the prompt) are looking good. (For some installs it doesn't, and that's why I'm currently working on font-fallback improvements). As for what Windows matters, I am currently working on a DirectWrite backend for font/text handling. I might come across your above behavior then, too, I hope. (Well, Thursday/Friday I'll be streaming some parts doing that then). |
It is ZSH with Powerlevel9k, and I have never configured that specific glyph, so I guess it's their default for multiline prompts. However, I do have some fonts that have specific glyphs, as Powerline does show Git icons and such: I do have a few fonts like Inconsolate or Liberation Sans installed systemwide because of LaTeX so these might be from there... Not sure. |
[
, AltGr-c for &
, etc.) not supported on Windows
Using release https://github.com/contour-terminal/contour/releases/tag/v0.3.9.250, this is still a thing. The odd part is that in PowerShell the modifier keys work nicely, but once you SSH away to any system whatsoever (we tried this with several configurations, different Windows machines, different remote machines, Debian, Ubuntu, RedHat, SUSE, etc., various versions in a corporate setting, SSH and local WSL...) it just breaks apart. I'm trying this with both my own configuration, and the default one, same result.
The odd thing is that it looks like AltGr-f (which is the sequence for This seems to be specific to something on Windows... Exact same contour configs SSHing to a remote Unix-based machine from another Unix-based machine (e.g. from Ubuntu to Debian, Ubuntu to RedHat, Debian to Ubuntu, etc.) works normally. I think this picture is the best way I can sum it up, that you can see I pressed [ twice and yet only one appeared on the remote side: |
[
, AltGr-c for &
, etc.) not supported on Windows[
, <kbd>AltGr</kbd>-<kbd>c</kbd> for &
, etc.) not supported on Windows
[
, <kbd>AltGr</kbd>-<kbd>c</kbd> for &
, etc.) not supported on Windows[
, AltGr-c for &
, etc.) not supported on Windows
N.b.: Git Bash, unlike Contour, is not sending magical escape sequences to the input stream of FYI: You can type P.S.: @gamesh411 You might be interested in tracking this... |
Trying again with mayhaps newer versions.
Using the default configuration as created by the aforementioned version. Same behaviour:
The same sequences AltGr-F-F and AltGr-F-Q executed if the target program running in the remote server is not bash, sh, or zsh, but
For comparison, doing the following input using Git Bash (remote AltGr-F ␣ SPACE c a t ⏎ RETURN And the previous sequences using Contour (remote
|
For reference, here is the same keyboard sequence typed into the automatically spawned PowerShell within Contour. I can't try the AltGr-F ␣ SPACE
|
Does WSL behave the same as ssh? |
@ferdinandyb Unfortunately, I cannot check this. I do not have WSL on the Windows system that I am |
Hm. So I was thinking about it, maybe it's not actually Contour but SSH? Let's see... Contour, running PowerShell, uses
but PowerShell's console does NOT exhibit the bogus behaviour. Git Bash, which also does NOT exhibit the weird behaviour, on the other hand, rolls its own joint by running the following SSH client:
Now I tried forcing Git Bash to run SSH via the Windows binary, but I can't get to log in:
|
@ferdinandyb Do you mean "in WSL" as in the WSL terminal prompt running inside Contour? What about |
By WSL I mean I start contour, type "wsl", get dropped into the whatever WSL is with my default shell (zsh). Ok, so in WSL, after executing |
@uspasojevic96 suggested locales... Some more information, as I was tinkering about with some of the machines. So I spun up a completely new machine which is completely headless. It just has an SSH, nothing else. Pure, bare metal, not Docker. SSHing into it like so:
I do not get a login shell (no prompt whatsoever), but I am still connected and can type. Here, pressing AltGr-F results in a single
However, if I connect using a log-in shell, even if the
Normally, my computers are set to |
Description
When pressing the key sequences
AltGr-f
,AltGr-c
,AltGr-m
, etc. (for[
,&
and<
characters, respectively), the cursor blinks but nothing happens, the requested characters are not typed in.Environment
v0.1.0_prerelease_120
c2add12xterm-256color
huHU
By default, the terminal starts PowerShell. The modifier characters work in the standard PowerShell window. I'm
ssh
over to a Linux machine, but it doesn't help the case. (Normal Git Bash MINTTY works properly.)Steps to Reproduce
bin/Contour.exe
&
by pressingAltGr-c
, observe nothing happens.The text was updated successfully, but these errors were encountered: