From: ramestica@gmail.com
To: help-gnu-emacs@gnu.org
Subject: Re: tramp and how to source remote environment
Date: Thu, 26 Feb 2009 18:18:02 -0800 (PST) [thread overview]
Message-ID: <b56f2d0a-4c25-46f6-99cc-3e8b2e7c2e42@41g2000yqf.googlegroups.com> (raw)
In-Reply-To: mailman.1109.1234992614.31690.help-gnu-emacs@gnu.org
On Feb 18, 4:30 pm, Michael Albinus <michael.albi...@gmx.de> wrote:
> Please check the Tramp manual, (info "(tramp)Remote Programs")
Hi Michael,
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.
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.
Is there something I missed about how to configure tramp or does tramp
simply not work the way I want it?
thanks,
Rodrigo
next prev parent reply other threads:[~2009-02-27 2:18 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 [this message]
2009-03-03 16:36 ` Michael Albinus
[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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b56f2d0a-4c25-46f6-99cc-3e8b2e7c2e42@41g2000yqf.googlegroups.com \
--to=ramestica@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.