wincompose
wincompose copied to clipboard
samhocevar
Not working in Cmder
I'm on Windows 7, and cmder appears to be ignoring any sequence entered after pressing the compose key. Even if the sequence is correct, the only thing actually written on the terminal is the key pressed right after said sequence. For instance, if I type
Compose .. ?
I would expect the following:
…?
instead, I get:
?
is it just me? is there any workaround?
Thank you
Sorry that it’s not working as expected. FYI I have no problem on Windows 10, using Cmder 1.3.17.1082 and WinCompose 0.9.6.
The problem may be related to user privileges. Can you please tell me the UAC Virtualization status of Cmder (ConEmu64.exe) and WinCompose? Here is a brief documentation in case you’re not familiar with what I am asking.
My Cmder version is 1.3.17, and WinCompose is 0.9.6
Both ConEmu64.exe and ConEmuC64.exe say Disabled in the UAC Virtualization column.
WinCompose instead says Not Allowed.
I'm experiencing the same issue on Windows 10
The Elevated column is Yes for WinCompose and No for ConEmu64.exe and ConEmuC64.exe.
This is my configuration for WinCompose. I've also tried changing Compose Key from Caps Lock to Right Control, same outcome.
Let me know if you need anything else, like the settings of Cmder (even though the changes I've done to the default configuration are only esthetic).
For now I really don’t have any idea what could be the problem. Two things I can suggest:
- maybe try directly with vanilla ConEmu (part of Cmder) to make sure the issue lies in the terminal emulator
- open the WinCompose Debug Window (notification icon → Help → Debug Window) and inspect whether pressing Compose.. in Cmder eventually leads to the message
Valid sequence! Sent “…”
Same issue in ConEmu. According to the Debug Window, WinCompose is behaving correctly: it reads the Compose key, reads the following two dot characters, detects a valid sequence and even sends it (somewhere). But Cmder doesn't display anything …