You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AltGr-\ from the physical keyboard says Left Ctrl and Right Alt are pressed.
AltGr\ from the On-Screen Keyboard says Left Ctrl, Left Alt, and Right Alt are pressed.
Those are the flags for the AltGr substitute being used. By default, Clink ignores the AltGr substitute, to avoid interfering with tons of key bindings.
Running clink set terminal.use_altgr_substitute true lets Clink respect the AltGr substitute, and then the OSK is able to input the \ character.
Hopefully there is a way for Clink to differentiate between a user entering the AltGr substitute versus the OSK generating a misleading AltGr substitute. Maybe Clink can consider Left Alt + Right Alt to mean that it isn't actually the AltGr substitute?
Originally reported by @Sopor in cmderdev/cmder#89 (comment):
I can't type backslash, but i can copy it from another window and paste it in Cmder.
The text was updated successfully, but these errors were encountered: