From: Christopher Allan Webber <cwebber@dustycloud.org>
To: myglc2 <myglc2@gmail.com>
Cc: Alex Kost <alezost@gmail.com>, help-guix <help-guix@gnu.org>
Subject: Re: GuixSD and TRAMP
Date: Tue, 25 Oct 2016 11:45:33 -0500 [thread overview]
Message-ID: <87bmy88jiq.fsf@dustycloud.org> (raw)
In-Reply-To: <87d1io8osg.fsf@dustycloud.org>
Christopher Allan Webber writes:
> I'm also not sure it will find the right paths if your username is
> different on the remote host, and some of the binaries it's looking for
> are in your user's profile there?
Well, I just found in the `tramp-remote-path' docs:
You can use ‘~’ in this list, but when searching for a shell which groks
tilde expansion, all directory names starting with ‘~’ will be ignored.
Given that, I've updated the code I'm using to:
#+BEGIN_SRC emacs-lisp
;; 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
"~/.guix-profile/bin" "~/.guix-profile/sbin")))
#+END_SRC
But maybe the best option would be:
#+BEGIN_SRC emacs-lisp
;; 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
'("~/.guix-profile/bin" "~/.guix-profile/sbin"
"/run/current-system/profile/bin" "/run/current-system/profile/sbin")))
#+END_SRC
That seems like the best general case route? We could keep
tramp-own-remote-path in there too, I guess?
next prev parent reply other threads:[~2016-10-25 16:45 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 [this message]
2016-10-25 8:16 ` Ludovic Courtès
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=87bmy88jiq.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=alezost@gmail.com \
--cc=help-guix@gnu.org \
--cc=myglc2@gmail.com \
/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).