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.
The
cm_tmuxtriggering 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_tmuxpart ofn-c-mrun 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!