From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: GuixSD and TRAMP
Date: Tue, 25 Oct 2016 10:16:47 +0200 [thread overview]
Message-ID: <874m40c07k.fsf@gnu.org> (raw)
In-Reply-To: <87r379anuq.fsf@gmail.com> (Alex Kost's message of "Fri, 21 Oct 2016 15:27:41 +0300")
Alex Kost <alezost@gmail.com> skribis:
> Ludovic Courtès (2016-10-20 23:00 +0200) wrote:
>
>> Christopher Allan Webber <cwebber@dustycloud.org> skribis:
>>
>>> Ho-ho, it turns out the snippet Ludo pasted me on IRC was the answer
>>> after all:
>>>
>>> ;; Make sure we work on remote guixsd machines :)
>>> ;; probably only helps if you start on a guixsd machine..!
>>> (setq tramp-remote-path
>>> (append tramp-remote-path
>>> '(tramp-own-remote-path)))
>
> I also add 'tramp-own-remote-path' to tramp-remote-path in my emacs
> config; as well as Ricardo and David.
>
>> Good to know!
>>
>> Should we patch Emacs or something so that it works by default?
>
> Just to mention, a year ago David and I (and probably Ricardo) also
> agreed that it would be good to patch our Emacs for this. It's just
> that no one have sent such a patch since then :-)
Good, let’s all add it to our to-do list then. ;-)
Looks like it shouldn’t be hard to address and would save people a lot
of time.
Ludo’.
prev parent reply other threads:[~2016-10-25 8:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 22:21 GuixSD and TRAMP Christopher Allan Webber
2016-10-19 22:52 ` Christopher Allan Webber
2016-10-20 21:00 ` Ludovic Courtès
2016-10-20 22:55 ` Christopher Allan Webber
2016-10-21 12:27 ` Alex Kost
2016-10-24 19:24 ` myglc2
2016-10-25 14:51 ` Christopher Allan Webber
2016-10-25 16:45 ` Christopher Allan Webber
2016-10-25 8:16 ` Ludovic Courtès [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874m40c07k.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alezost@gmail.com \
--cc=help-guix@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).