GNU bug report logs - #30434
magit won’t work over TRAMP

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Mark H Weaver <mhw <at> netris.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#30434: closed (magit won’t work over TRAMP)
Date: Wed, 14 Feb 2018 08:52:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Wed, 14 Feb 2018 03:51:06 -0500
with message-id <87wozgosxx.fsf <at> netris.org>
and subject line Re: bug#30434: magit won’t work over TRAMP
has caused the debbugs.gnu.org bug report #30434,
regarding magit won’t work over TRAMP
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
30434: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=30434
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Ricardo Wurmus <rekado <at> elephly.net>
To: bug-guix <at> gnu.org
Subject: magit won’t work over TRAMP
Date: Mon, 12 Feb 2018 13:53:22 +0100

The default value for “magit-git-executable” (when magit is installed
via Guix) appears to be a store path, such as
“/gnu/store/l7g5r1c2i0bf3cd71g53ajy8khdcyidz-git-2.16.1/bin/git”.  This
means that when magit is used over TRAMP it will try to find the exact
same git executable on the remote.

Instead, magit should only look for “git” on the remote, not for the
exact store location of a particular git executable.

I could only use magit over TRAMP after setting “magit-git-executable”
to “git”.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

[Message part 3 (message/rfc822, inline)]

From: Mark H Weaver <mhw <at> netris.org>
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: Alex Kost <alezost <at> gmail.com>, 30434-done <at> debbugs.gnu.org
Subject: Re: bug#30434: magit won’t work over TRAMP
Date: Wed, 14 Feb 2018 03:51:06 -0500

Ricardo Wurmus <rekado <at> elephly.net> writes:
> I think it makes sense *not* to hardcode the path to the git executable
> here.

Agreed.  Done, in commit 5fe9ba59ba1cea12a70d011aacbace52e3bfda18 on
master and commit 317e8e9404058af35d9843e076934560f95d895a on
core-updates.  I'm closing this bug now.

    Thanks,
      Mark

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.