-
-
Notifications
You must be signed in to change notification settings - Fork 257
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
Weird Interaction with AltTab on MacOS #858
Comments
Update:Used a different switcher app called Contexts and there is no longer a problem; trigger expands immediately and don't need to hit |
Hey @blackace72, Thanks for reporting this issue! This issue is very interesting, as fixing this problem might help us on other issues (such as #825). Could you please try reproducing the problem again with the I'm particularly interested in the logs that are produced when you say "the replacement will eventually trigger after ~6 seconds" Cheers :) |
Log I got from using
Another test
Even though the logs show about 3-4 seconds, it is actually about 6 seconds of delay (not sure if it helps :)) Also, nothing shows in the log for AltTab using |
@blackace72 Thanks! That's helpful :) |
Hey @blackace72, The next version 2.1.0-alpha will include a fix for this problem, thank you for the help! :) Cheers :) |
Problem:
I use AltTab for switching windows, with hotkey bound to
cmd-tab
. Usingcmd-tab
disables triggering of matches, unless I hitcmd
again. Won't even trigger within 20 seconds of writing match. This happens every time I use the hotkey. However, if I switch the hotkey tooption-Tab
, then the replacement will eventually trigger after ~6 seconds.Expected behavior:
Immediately trigger replacement when match is written, even after switching windows/apps
Background:
toggle_key: "RIGHT_ALT"
Workarounds
option-Tab
What I've noticed:
cmd-tab
, persists even when I click on other appscmd-tab
doesn’t fix it (doesn’t reverse the problem)cmd-tab
and anothercmd
and hittingtab
cmd
allows the triggers again (notEsc
,control
, oroption
)cmd-tab
problem still persists, but now WILL trigger after a short delay (about 6 seconds);tab-cmd
doesn’t cause problemscontrol-cmd
doesn’t cause problemsoption-cmd
doesn’t cause problemsOther github problems referenced and tried solutions:
The text was updated successfully, but these errors were encountered: