-
-
Notifications
You must be signed in to change notification settings - Fork 260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The candidate input method is being replaced while typing, not after typing. #1968
Comments
It appears Espanso is injecting the correct characters but not in the right order, and it is failing to fully delete the trigger, leaving the colon prefix. I suggest upgrading Espanso to the current version - a lot of work has gone into making changes, and it is possible the problem has been resolved. However, it may be necessary to try the different injection methods. I suggest trying different |
Installed the latest version 2.2.1, the issue persists, but the problem was successfully resolved using the solution you provided. Just need to add text to
It works perfectly. |
It works for me generally, too, although I have needed a couple of exceptions. |
Hi, I meet new issue(It is the original problem): or Is there a way to make espanso not recognize the text in the input candidate area, but instead wait until the input is complete before replacing it? Expected to achieve: While typing, it displays |
Unfortunately no, the current implementation of Espanso doesn't allow for that. Having Espanso work well with all Input Methods is important, so we'll definitely see what can be done to make this work better in the future. But for the moment your only option is to name triggers in a way that makes these kinds of conflicts less likely 😕 |
Description
Steps to reproduce
Expected behavior
I want the pop-up candidate input interface, espanso won't recognize the substitution, it will wait for the input method to confirm the selected word (waiting for the candidate input method to disappear) before espanso replaces it.
Screenshots
No response
Logs
espanso.log
Your environment
Self-service
The text was updated successfully, but these errors were encountered: