Michael Albinus <michael.albinus@gmx.de> writes: > Great! Since you are a regular eglot+Tramp user, could I ask you for a > test? > > I assume you are using Tramp with ssh or scp. If you also don't use a > password (for example via public key authentication), please try the > following setting: > > --8<---------------cut here---------------start------------->8--- > (add-to-list 'tramp-connection-properties > (list (regexp-quote "/ssh:user@host:") > "direct-async-process" t)) > --8<---------------cut here---------------end--------------->8--- > > "/ssh:user@host:" must be adapted of course, and you must set this prior > opening a connection to this remote path. This should give you better > performance when starting the language server. I use eglot+Tramp with various containers (nspawn, docker, podman), which don't support the âtramp-direct-asyncâ flag, so I'm not sure how helpful this testing would be. I know we've spoken about that flag before, and I came away from those discussions with the impression that those methods should not support direct-async, but I'm unsure why. I have only skimmed the relevant code, but it seems like there shouldn't be a problem with supporting direct-async on the container methods. Is there some danger I should be aware of? If it's safe enough, I'd be happy to flag support for direct-async in the methods and do the above test. WDYT? -bjc
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4