Yep, I googled ‘tramp-own-remote-path’ and found the bit in the massive manual about how to change this behaviour. Thanks for the tip.
But why should I have to go searching to get tramp to do something that ought to be the default behaviour? It fails miserably against the design principle of “don’t do anything unexpected”, and totally rewriting my remote path for tramp’s own convenience is highly unexpected. -- Kevin from my iPhone On 27 May 2021, at 08:59, Michael Albinus <[email protected]> wrote: Kevin Broadey <[email protected]> writes: Hi Kevin, > The only way I've been able to get Tramp to Do The Right Thing and > leave my remote PATH the way I want it to be is to put this in my . > emacs file... > > ;; tramp is overzealous about setting the remote PATH, > ;; contrary to .profile, .bash_profile .bashrc etc > (eval-after-load "tramp-sh" '(defun tramp-set-remote-path(vec))) > > This is maybe an extreme reaction, but I've got a job to do, and when > it comes to setting the remote PATH, I really do know better than my > editor. This is maybe an extreme reaction, but if you've got a job to do with Tramp, you should consult the documentation. As somebody has told already, adding tramp-own-remote-path to tramp-remote-path should do the job. > Thanks Best regards, Michael.
