Whenever I try to edit remote files with anaconda-mode and pyvenv, there are constant pauses as, after pretty much every movement, anaconda causes TRAMP to re-open the connection. I haven't been able to pinpoint why exactly it happens, but it seems only to be the case with an active pyvenv-virtual-env, and if I enable debug-on-quit and interrupt one of the connections, anaconda-mode is clearly listed in the backtrace.
I created a gist which reproduces the issue with a minimal setup based on my actual config (please give it a couple seconds to set up the environment). Try moving around the file, defining a function, etc. It assumes an SSH server on localhost to simulate the remote access. Since localhost-based TRAMP access is as fast as it can be, the issue isn't as visible as it is during a real remote session, so injecting some artificial latency helps. On Linux, it can be achieved with:
$ sudo tc qdisc add dev lo root handle 1:0 netem delay 20msec
And removed again with:
$ tc qdisc del dev lo root
Whenever I try to edit remote files with
anaconda-modeandpyvenv, there are constant pauses as, after pretty much every movement, anaconda causes TRAMP to re-open the connection. I haven't been able to pinpoint why exactly it happens, but it seems only to be the case with an activepyvenv-virtual-env, and if I enabledebug-on-quitand interrupt one of the connections,anaconda-modeis clearly listed in the backtrace.I created a gist which reproduces the issue with a minimal setup based on my actual config (please give it a couple seconds to set up the environment). Try moving around the file, defining a function, etc. It assumes an SSH server on localhost to simulate the remote access. Since localhost-based TRAMP access is as fast as it can be, the issue isn't as visible as it is during a real remote session, so injecting some artificial latency helps. On Linux, it can be achieved with:
And removed again with: