all messages for Guix-related lists mirrored at
 help / color / mirror / code / Atom feed
From: Josselin Poiret <>
To: Mikhail Kryshen <>,
	Antonio Carlos Padoan Junior <>,
Subject: Re: emacs tramp in remote guix
Date: Sat, 12 Feb 2022 12:30:11 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hello everyone,

Mikhail Kryshen <> writes:

> Hello,
> Antonio Carlos Padoan Junior <> writes:
>> Hello everybody,
>> I'm trying to use emacs tramp to connect to a guix machine but tramp
>> complains it can't find an appropriate 'ls' command.
>> I tried to help tramp setting the following:
>>   (add-to-list 'tramp-remote-path "/run/current-system/profile/bin")
> For me this works.
>> But I'm still not lucky. I always get the same error.  Is there any
>> elegant way to correctly use tramp with a remote guix machine?
> You may need to delete ~/.emacs.d/tramp before starting Emacs for the
> setting to take effect.

I personally use
--8<---------------cut here---------------start------------->8---
  (require 'tramp)
   '((tramp-remote-path . (tramp-own-remote-path))))
   '(:application tramp :protocol "sudo" :machine "hostname")
--8<---------------cut here---------------end--------------->8---
for tramp on my own machine.  The symbol 'tramp-own-remote-path uses the
login shell of the target to determine the environment to use, so is
well suited for guix.  You may need to adjust the :protocol and :machine
keys of the connection-local-set-profiles call for your use case though.

Josselin Poiret

  reply	other threads:[~2022-02-12 11:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2022-02-11 15:40 ` emacs tramp in remote guix Antonio Carlos Padoan Junior
2022-02-12  2:42   ` Mikhail Kryshen
2022-02-12 11:30     ` Josselin Poiret [this message]
2022-02-12 18:04       ` Antonio Carlos Padoan Junior
2022-02-12 18:14         ` Maxime Devos
2022-02-13  9:52           ` Josselin Poiret
2022-02-16 10:43             ` Max Brieiev

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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

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.