From: Antonio Carlos Padoan Junior <acpadoanjr@yahoo.com.br>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: Mikhail Kryshen <mikhail@kryshen.net>, guix-devel@gnu.org
Subject: Re: emacs tramp in remote guix
Date: Sat, 12 Feb 2022 19:04:02 +0100 [thread overview]
Message-ID: <87leyghsh9.fsf@yahoo.com.br> (raw)
In-Reply-To: <87czjsmif0.fsf@jpoiret.xyz> (Josselin Poiret's message of "Sat, 12 Feb 2022 12:30:11 +0100")
Josselin Poiret <dev@jpoiret.xyz> writes:
>
> I personally use
>
> (require 'tramp)
> (connection-local-set-profile-variables
> 'guix-system
> '((tramp-remote-path . (tramp-own-remote-path))))
> (connection-local-set-profiles
> '(:application tramp :protocol "sudo" :machine "hostname")
> 'guix-system)
>
> 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.
>
> Best,
Thanks Josselin and Mikhail!
Cleaning the tramp file did the job! It works now!
I will check closely Josselin proposition as well, it seems I have
something new to learn there.
IMHO, giving the importance emacs has in guix distribution this is
something that merits a place on guix cookbook perhaps.
Best regards
--
Antonio Carlos PADOAN JUNIOR
Phone: +33(0)6 5035 1196
GPG fingerprint:
243F 237F 2DD3 4DCA 4EA3 1341 2481 90F9 B421 A6C9
next prev parent reply other threads:[~2022-02-12 18:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87h795s97x.fsf.ref@yahoo.com.br>
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
2022-02-12 18:04 ` Antonio Carlos Padoan Junior [this message]
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:
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=87leyghsh9.fsf@yahoo.com.br \
--to=acpadoanjr@yahoo.com.br \
--cc=dev@jpoiret.xyz \
--cc=guix-devel@gnu.org \
--cc=mikhail@kryshen.net \
/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.