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
{{ message }}
This repository has been archived by the owner on Jul 27, 2018. It is now read-only.
The cm_tmux triggering needs some kind of rate-limiting.
I'm not sure about the exact workflow, but when other plugins are doing heavy communication (eg. vlime) [1] there is some kind of interaction that makes the cm_tmux part of n-c-m run within a very tight loop (every few msec, consuming a CPU).
Ad 1: It's not even that real screen updates are needed - just communication to another vim plugin already triggers that problem.
Thanks for listening!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The
cm_tmux
triggering needs some kind of rate-limiting.I'm not sure about the exact workflow, but when other plugins are doing heavy communication (eg.
vlime
) [1] there is some kind of interaction that makes thecm_tmux
part ofn-c-m
run within a very tight loop (every few msec, consuming a CPU).Ad 1: It's not even that real screen updates are needed - just communication to another vim plugin already triggers that problem.
Thanks for listening!
The text was updated successfully, but these errors were encountered: