Open user202729 opened 2 years ago
I'm not sure what the right fix is under the hood, but as a work-around you can try defining an entry for {#Shift_L(=)}
which will send shift-equal explicitly.
But it's not undoable (i.e. *
does not delete the same number of characters), for one. (a{#backspace}
does not count)
Describe the bug
As above. If Plover attempts to output "+" it sends its own key instead of shift-equal.
That appears to break compatibility with some applications, e.g. vim receive it as
^[Ol
and does not recognize it as+
.(I don't know if it's vim's fault or Plover's fault, will inspect later. Nevertheless using a more "common" combination would be compatible with more applications.)
To Reproduce
+
then stroke it.[esc] O l
is pressed.Expected behavior
As usual.
Operating system