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

Previous Next

Package: guix;

Reported by: Ricardo Wurmus <rekado <at> elephly.net>

Date: Mon, 12 Feb 2018 12:54:01 UTC

Severity: normal

Done: Nicolas Goaziou <mail <at> nicolasgoaziou.fr>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

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

> Ricardo Wurmus (2018-02-12 13:53 +0100) wrote:
>
>> 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”.
>
> If people will agree that changing 'magit-git-executable' is not needed,
> then I think 'git' can be removed from the inputs as it is used just for
> that variable.
>
> P.S.  I also use just "git" for 'magit-git-executable'.

That's fine with me.  IIRC, I was the one who arranged to set
'magit-git-executable' to an absolute path in the store, but in
retrospect I'm not sure it makes sense in this case, especially if it
breaks TRAMP.

     Regards,
       Mark




This bug report was last modified 114 days ago.

Previous Next


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