Re: tramp (2.2.13.25.1); Need to source ~/.profile to make remote commands work

[Dave Abrahams]

on Tue Aug 09 2016, Michael Albinus <michael.albinus-AT-gmx.de> wrote:

> Michael Albinus <address@hidden> writes:
>
> Hi Dave and Stéphane,
>
>> A possibility to source ~/.profile would be to set $ENV in
>> `tramp-remote-process-environment'. But this doesn't work yet, Tramp
>> nukes $ENV to the empty string these days.
>
> I've committed a patch to the Tramp and Emacs repositories, master
> branch. The Tramp manual says now:
>
>    Setting the ‘ENV’ environment variable instructs some shells to read
> an initialization file.  Per default, TRAMP has disabled this.  You
> could overwrite this behaviour by evaluating
>
>      (let ((process-environment tramp-remote-process-environment))
>        (setenv "ENV" "$HOME/.profile")
>        (setq tramp-remote-process-environment process-environment))
>
>>> Thanks,
>>> 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?

-- 
-Dave