Dave Abrahams <[email protected]> writes: Hi Dave,
> Hmm, it seems I can get the basic effect I need by putting > 'tramp-own-remote-path on the head of tramp-remote-path. How can that > possibly work if tramp isn't executing my .profile? If Tramp detects `tramp-own-remote-path', it opens a login shell and reads the path settings from there. Since you have said that "My working environment depends on ~/.profile", I thought you need more but only $PATH from your .profile. That's why I've implemented this solution via $ENV. Best regards, Michael. _______________________________________________ Tramp-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/tramp-devel
