You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As indicated in this thread, with current implementation, apps that do not signal front application changed like Raycast/Alfred(no compatibility mode) do not get detected in window switching.
It's not really a major problem in alfred, since after invoking alfred bar, typing will start in insert mode;
However in Raycast, svim will start as whichever mode that's last used in it.
It would be great if either:
Detect window switching with more robust methods.
Detect window destroyed event to reinitialize raycast bar's vim buffer to start at insert mode
For the first solution, this issue in KindaVim mentions using "other nails and hammers" method to detect new windows. Sadly KV is closed source so we have little idea as to which.
The text was updated successfully, but these errors were encountered:
As indicated in this thread, with current implementation, apps that do not signal front application changed like Raycast/Alfred(no compatibility mode) do not get detected in window switching.
It's not really a major problem in alfred, since after invoking alfred bar, typing will start in insert mode;
However in Raycast, svim will start as whichever mode that's last used in it.
It would be great if either:
For the first solution, this issue in KindaVim mentions using "other nails and hammers" method to detect new windows. Sadly KV is closed source so we have little idea as to which.
The text was updated successfully, but these errors were encountered: