Is there any way to break the formatter's context/translator state? #1348
Unanswered
user202729
asked this question in
Q&A and Support
Replies: 1 comment 1 reply
-
What kind of side effects?
I'll second this. It's not ideal because of the common issue of some programs skipping keys, or because it actually produces output (not ideal for programs that do something on space key). |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
For example, if
R
is mapped to{#right}
(or{#right}{}{^}
,*UPD
is mapped to{*<}
(or{:retro_case:upper_first_word}
) andWORD
is mapped toword
. Then when I strokeI expect Plover to output
Currently the last stroke deletes all the 8 characters (possibly more) and turn all those to uppercase.
What can I do so it doesn't happen?
I just developed a simple plugin that calls(edit:clear_translator_state
,clear_translator_state
has some bad side effects) but is there an existing way? ({^ ^}{#backspace}
doesn't count)Beta Was this translation helpful? Give feedback.
All reactions