Kevin Broadey <[email protected]> writes: Hi Kevin,
> 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. Why searching the web? 'C-h i g (tramp) RET' gives you the Tramp manual. > 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. Tramp's primary audience are remote file operations. This requires proper tools on the remote side. We have seen too many error reports, caused by improper tools at non-standard locations. That's why Tramp is restrict in default PATH settings. Best regards, Michael.
