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: Thu, 08 Aug 2024 19:33:50 +0200 [thread overview]
Message-ID: <87ed6yly0x.fsf@gmx.de> (raw)
In-Reply-To: <87ikwbkpgj.fsf@gmx.de> (Michael Albinus's message of "Thu, 08 Aug 2024 17:24:12 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
Hi Romário,
>> Maybe I'm misunderstanding this, but wouldn't this mean remote
>> binaries would be executed locally? This is not what happens to me. As
>> I mentioned already, I'm able to run eglot+clangd with sshfs and it
>> executes in the remote machine. Same for compiling our application.
>
> You're right. I did check tramp-sshfs-handle-process-file shortly, and
> was confused by calling call-process. But this initiates a remote process.
To be more precise: tramp-sshfs-handle-process-file uses call-process
for the remote process. But call-process doesn't know the function
(exec-path). Instead, it uses the variable exec-path for starting the
local process. No handling for the remote path.
If your problem is just the git program name, you might configure
magit-remote-git-executable to an absolute path.
Best regards, Michael.
prev parent reply other threads:[~2024-08-08 17:33 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
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 [this message]
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=87ed6yly0x.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).