From: Michael Albinus <michael.albinus@gmx.de>
To: ramestica@gmail.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: tramp and how to source remote environment
Date: Tue, 03 Mar 2009 17:36:17 +0100 [thread overview]
Message-ID: <nq7i36zhq6.fsf@alcatel-lucent.de> (raw)
In-Reply-To: <b56f2d0a-4c25-46f6-99cc-3e8b2e7c2e42@41g2000yqf.googlegroups.com> (ramestica@gmail.com's message of "Thu\, 26 Feb 2009 18\:18\:02 -0800 \(PST\)")
ramestica@gmail.com writes:
> Hi Michael,
Hi Rodrigo,
> reading the manual does not seem to help me. Looking into tramp.el the
> problem (my problem) seems to be that tramp does not respect whatever
> my PATH is set to during the login process (in my case
> within .bash_profile).
>
> Perhaps there is in the lisp code of tramp-get-remote-path (used by
> tramp-set-remote-path to actually set the path) something that I'm not
> understanding. Too much lisp there for me.
Tramp has the variable tramp-remote-path. You can add there your
preferred paths, like
(add-to-list 'tramp-remote-path "/my/path" 'append)
> On the other hand, if in tramp-set-remote-path I replace
>
> "PATH=%s; export PATH"
>
> by
>
> "PATH=${PATH}:%s; export PATH"
>
> then things start to work the way I want it! My PATH (crafted within
> my .bash_profile) is now preserved and now I can actually compile.
Maybe the following works (not tested):
(add-to-list 'tramp-remote-path "${PATH}")
> thanks,
> Rodrigo
Best regards, Michael.
next prev parent reply other threads:[~2009-03-03 16:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 1:17 tramp and how to source remote environment ramestica
2009-02-18 1:43 ` ramestica
2009-02-18 21:30 ` Michael Albinus
[not found] ` <mailman.1109.1234992614.31690.help-gnu-emacs@gnu.org>
2009-02-27 2:18 ` ramestica
2009-03-03 16:36 ` Michael Albinus [this message]
[not found] ` <mailman.2278.1236098043.31690.help-gnu-emacs@gnu.org>
2009-03-05 4:59 ` ramestica
2009-03-05 14:05 ` Michael Albinus
[not found] ` <mailman.2422.1236261821.31690.help-gnu-emacs@gnu.org>
2009-03-05 14:49 ` ramestica
2009-03-17 20:25 ` Michael Albinus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nq7i36zhq6.fsf@alcatel-lucent.de \
--to=michael.albinus@gmx.de \
--cc=help-gnu-emacs@gnu.org \
--cc=ramestica@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).