From: Michael Albinus <michael.albinus@gmx.de>
To: "Luiz Romário Santana Rios" <luizromario@tecgraf.puc-rio.br>
Cc: help-gnu-emacs@gnu.org
Subject: Re: tramp-sshfs doesn't seem to respect tramp-remote-path
Date: Tue, 30 Jul 2024 18:47:45 +0200 [thread overview]
Message-ID: <87h6c6g72m.fsf@gmx.de> (raw)
In-Reply-To: <072f5d9f-42d9-4d64-a9f0-e49ca0a1142d@tecgraf.puc-rio.br> ("Luiz Romário Santana Rios"'s message of "Tue, 30 Jul 2024 10:22:28 -0300")
Luiz Romário Santana Rios <luizromario@tecgraf.puc-rio.br> writes:
> Hello,
Hi,
> I've been trying out tramp-sshfs and it works fine, but for some
> reason it doesn't seem to respect tramp-remote-path. My remote machine
> has a very old git version so I needed to install a newer git
> elsewhere and make the path point there for magit to work. Under
> tramp-ssh this works fine, but it doesn't under tramp-sshfs (magit
> complains about the git version).
>
> Opening up eshell I noticed the following:
>
> - git --version -> git version 1.8.3.1
>
> - which git -> /sshfs:luizromario@remote-machine:/usr/bin/git
>
> - echo $PATH -> /usr/bin
>
> Is this a bug? Am I doing something wrong?
tramp-remote-path is used only for external processes of Tramp methods,
which are handled by tramp-sh-file-name-handler. That is, all methods
defined in tramp-sh.el and tramp-container.el.
> Thanks in advance
Best regards, Michael.
next prev parent reply other threads:[~2024-07-30 16:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 13:22 tramp-sshfs doesn't seem to respect tramp-remote-path Luiz Romário Santana Rios
2024-07-30 16:47 ` Michael Albinus [this message]
2024-07-30 21:28 ` Luiz Romário Santana Rios
2024-07-31 11:47 ` Michael Albinus
2024-07-31 15:18 ` Luiz Romário Santana Rios
2024-07-31 16:43 ` Michael Albinus
2024-08-08 13:13 ` Luiz Romário Santana Rios
2024-08-08 13:30 ` Michael Albinus
2024-08-08 13:37 ` Luiz Romário Santana Rios
2024-08-08 14:23 ` Michael Albinus
2024-08-08 15:18 ` Luiz Romário Santana Rios
2024-08-08 15:24 ` Michael Albinus
2024-08-08 17:33 ` 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=87h6c6g72m.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=help-gnu-emacs@gnu.org \
--cc=luizromario@tecgraf.puc-rio.br \
/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).