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

[Dave Abrahams]

> On Aug 10, 2016, at 9:40 AM, Michael Albinus <address@hidden> wrote:
> 
> Dave Abrahams <address@hidden> 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.

Hi Michael,

Apologies if I caused you to complicate tramp needlessly; I didn't realize that 
option existed.  Silly question, perhaps: when Tramp detects 
tramp-own-remote-path, why not just issue all remote commands through a login 
shell?

Thanks again for everything!
-Dave

> Best regards, Michael.