Tilde and square brackets on german keyboard are not working in WSL on ConEmu

[bdudelsack]

Versions

ConEmu build: 170723-170805
OS version: Windows 10 x64
Used shell version (Far Manager, git-bash, cmd, powershell, cygwin, whatever): WSL

Problem description

You cannot input Tilde and square brackets to the WSL console

Steps to reproduce

1. Press AltGr + * to get Tilde (~) or AltGr + 8 or AltGr + 9 to get square brackets

Actual results

Nothing is printed to the console

Expected results

Tilde or square brackets are printed to the console (works in previous versions)

[Maximus5]

works in previous versions

Previous version of what?

[bdudelsack]

Works in ConEmu <= 170709

[Maximus5]

Try to install build <= 170709 now and recheck.

[bdudelsack]

170709 - does work
170723, 170805 - are broken

[techexo]

Using ConEmu 170807 (I do not know if this release includes the change @Maximus5 made in the commit 8528912), with a French keyboard, all AltGr+"number" keys are working except the tilde.
Furthermore, arrow keys with Git-Bash are now broken ([Ctrl]+[p] or +[n] work fine for retrieving history and arrow keys are OK launching directly bash).
conemu-msys2-64.exe --keys give <x1B><x5B:[><x41:A><x1B><x5B:[><x42:B><x1B><x5B:[><x44:D> when pressing arrow keys.

[Maximus5]

Arrows are working properly.
I will check the problem with tilde.

[techexo]

Arrows are working properly.

Yes indeed, I am sorry, a remanent option -new_console:p was causing the arrow keys not to work.

[zommuter]

170807 fixes this partly. When I run the automatically generated {Bash::bash}

set "PATH=%ConEmuBaseDirShort%\wsl;%PATH%" & %ConEmuBaseDirShort%\conemu-cyg-64.exe --wsl -cur_console:pm:/mnt

, the only weird thing is an AltGr-Deadkey-Tilde which my (customized) layout has (though IIRC the original Swiss-German layout also has this). Instead of the usual ~ followed by space, I now have to enter ~ twice. That's acceptable (and how often do I need to type a ñ on WSL?) though confusing.

What still doesn't work though is searching through history via arrow keys, which ~/.inputrc's

## arrow up
"\e[A":history-search-backward
## arrow down
"\e[B":history-search-forward

should achieve. But maybe that's a problem with some other config files...

If I instead use the Task

"C:\Program Files\ConEmu\ConEmu\conemu-cyg-64.exe" "/cygdrive/c/Program Files/ConEmu/ConEmu/wsl/wslbridge.exe"

(I thing the major difference is the lack of the :p console switch), the Deadkey-Tilde works fine, but the arrow keys don't.

[bdudelsack]

Tilde and square brackets are now working properly for me in 170807.

The arrows and dead keys for german layout work fine too.

[zommuter]

For proper arrow function, p4 apparently must be inactive, i.e. instead of -cur_console:p I think -cur_console:p1 is the proper setting. Though at the moment I don't see any difference from omitting it. But apparently now the 256 colors don't work anymore despite the wslbridge task.

And the tilde-deadkey still behaves wrong, and more confusingly this seems to depend on whether I used wslbridge or pure bash.exe first after a reboot... Just a note, I checked: The deadkey-tilde is also present in the native DE-CH keyboard layout, so anyone in Switzerland might encounter the same problem. Another AltGr-Deadkey is ´, which also behaves weird. Sometimes it just works, sometimes it seems to cause a TAB to be passed, sometimes nothing happens. But maybe I should open a new issue for AltGr-Deadkeys, since the originally posted bug is fixed...

[techexo]

@zommuter Thank you for reporting that, I thought I was crazy. I have the same behavior with Git-Bash and conemu-msys2 connector but was not able to reproduce it properly (didn't think it could be the reboot that caused the problem) for arrow keys. According to which one is loaded first in Conemu, the arrows are functioning erratically.

[zommuter]

@techexo Thanks for reminding me to add that reboot information to #1224, so you also agree that depends on which task you started first after booting?

[techexo]

Using 170807 and a French azerty keyboard, all AltGr+numbers combinations are working, except for the tilde (configured in dead key or not).

However, After one reboot, using Git-Bash 2.14.0.windows.1:

• {Git Bash} = set "PATH=%ConEmuDir%\..\Git\usr\bin;%PATH%" & "%ConEmuDir%\..\Git\git-cmd.exe" --no-cd --command=%ConEmuBaseDirShort%\conemu-msys2-64.exe /usr/bin/bash.exe -l -i
• {BashColor} = set MSYSTEM=MINGW64 & %ConEmuBaseDirShort%\conemu-msys2-64.exe
• {Bash} = "C:\Program Files\Git\usr\bin\bash.exe" -l -i

1. launching {Git Bash}: arrow keys are working perfectly
2. launching {BashColor} using connector configuration found in the doc: arrow keys do not work properly.
3. after this, launching {Bash}, then {BashColor}, the arrow keys are working perfectly in all consoles!

Edit: I do not know if it is relevant, but when using {BashColor} it launch "MINGW64" (as shown in the command). When launching directly {Bash}, it shows "MSYS". Maybe one need to be launched before the other? However, it doesn't explain why {Git Bash}, which is also MINGW64, works directly after the reboot.

[Maximus5]

Let's move DeadKey conversation to gh-1224. I wonder, without ConEmu are you able to enter single dead key? For example, I have to type AltGr+~ twice to get two tildas printed. Is there a way to print one tilde?

As for arrows. It's all about turned on XTerm emulation. I thought race was fixed, but probably not completely.
Does not matter what is shown in tab title. MSYSTEM value has effect on bash profile scripts, but not a connector or ConEmu.
If you see arrows aren't working, open Settings/Info page and show screenshot here.

[techexo]

Here are the wanted screenshots, the difference I see is the win32|msys2 when not working, vs xterm|msys2 when working.

Arrow keys not working

Arrow keys working

[techexo]

I wonder, without ConEmu are you able to enter single dead key? For example, I have to type AltGr+~ twice to get two tildas printed. Is there a way to print one tilde?

@Maximus5 When the tilde is configured as a deadkey, you have to type [AltGr]+[2] (on French keyboard) then [Space]. Using a layout without tilde as a deadkey, you just press [AltGr]+[2].

[Maximus5]

I can't reproduce the problem with arrow keys. On your first screenshot second groupbox shows "win32|msys2". To understand why it shows "win32" instead of "xterm" I need LogFiles reproducing the problem.

Check the option, save settings, and try to reproduce. When the problem appears, make a screenshot of Settings/Info and push here link to the logfles and screenshot.

[techexo]

@Maximus5 I cannot reproduce it on my work computer today either and I will have limited connectivity the next coming week. What I suggest is maybe keeping this topic for the "tilde" issue and I will file a new issue when (and if) I succeed to produce appropriate logs.

[techexo]

After 5 days using the connector, I wasn't able to reproduce the comportment after multiple reboots of the computer... It might have been a bug in the configuration that was overwritten after reinstallation of the program.

However, concerning the "tilde" issue, the problem is still there. I do not know if the commit 9a209c1, related to gh-1224, is supposed to fix this.
If this information can be of any help to narrow down the issue, git-bash with the connector doesn't show anything when pressing AltGr+2, but Vim displays in normal mode ^@ when the combination is pressed, instead of ~.

[techexo]

@Maximus5 Problem solved for tilde not configured as a dead key with Alpha 170814.
For the win32/xterm mix-up, I am not able to reproduce it. Sorry for that, it might have been some issue with my personal installation at the time.