Re: Is there any way to make direct-async-process support tramp-remote-path?

[Michael Albinus]

Liu Bo <liubolovelife@gmail.com> writes:

Hi,

> Hi, I found direct-async-process really make tramp faster(especially
> magit), but since it dose not use tramp-remote-path so I can't make
> command that need extra programs work, like eglot or
> consult-ripgrep(says command not found).
>
> So is there any way to make direct-async-process support tramp-remote-path?

Not directly, because it calls the program as part of the ssh
invocation, like (example from magit)

--8<---------------cut here---------------start------------->8---
ssh -q -l albinus -o ControlMaster=auto -o 
ControlPath=/home/albinus/.cache/emacs/tramp.%C -o ControlPersist=no -e none 
gandalf cd /home/albinus/src/emacs/ && ( env 
INSIDE_EMACS\=30.0.50\,magit\,tramp\:2.7.0-pre ENV\=\'\' TMOUT\=0 
LC_CTYPE\=\'\' CDPATH\= HISTORY\= MAIL\= MAILCHECK\= MAILPATH\= PAGER\=cat 
autocorrect\= correct\= git --no-pager --literal-pathspecs -c 
core.preloadindex\=true -c log.showSignature\=false -c color.ui\=false -c 
color.diff\=false apply --reverse --cached -p0 --ignore-space-change - )
--8<---------------cut here---------------end--------------->8---

But perhaps we could add a user option, which instruct Tramp to expand
tramp-remote-path as part of the command, like PATH=/a/b:/c/d. I will
think about.

Bst regards, Michael.