all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: 30434@debbugs.gnu.org
Subject: bug#30434: magit won’t work over TRAMP
Date: Mon, 12 Feb 2018 13:53:22 +0100	[thread overview]
Message-ID: <87lgfyl67x.fsf@elephly.net> (raw)

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

             reply	other threads:[~2018-02-12 12:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <365299e60040c03a84cbb7770adb3f94349dd2ed.camel@telenet.be>
2018-02-12 12:53 ` Ricardo Wurmus [this message]
2018-02-12 17:33   ` bug#30434: magit won’t work over TRAMP Alex Kost
2018-02-12 19:11     ` Ricardo Wurmus
2018-02-14  8:51       ` Mark H Weaver
2018-02-14 17:00         ` Alex Kost
2018-02-14 18:17           ` Mark H Weaver
2018-02-15 19:38             ` Alex Kost
2018-02-16  9:09               ` Mark H Weaver
2018-02-16 16:56                 ` Alex Kost
2018-02-16 19:00                   ` Mark H Weaver
2018-02-12 19:51     ` Mark H Weaver
     [not found]   ` <handler.x.B30434.165288084625349.unknown@debbugs.gnu.org>
     [not found]     ` <77826704875d168a2f7c608e146d9d5b09e7588c.camel@telenet.be>
2022-07-13 12:53       ` Maxim Cournoyer
2022-07-20 15:42         ` Maxime Devos
2022-07-21  4:04           ` Maxim Cournoyer
2023-09-21  7:34             ` Simon Tournier
2023-09-23 10:17               ` Maxime Devos
2023-09-23 10:19                 ` Maxime Devos
2023-09-23 11:47                 ` Simon Tournier

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=87lgfyl67x.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=30434@debbugs.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/guix.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.