From: t@fullmeta.me
To: "kiasoc5--- via" <help-guix@gnu.org>
Subject: Re: Guix as remote dev machine
Date: Tue, 22 Mar 2022 23:54:15 +0000 [thread overview]
Message-ID: <644bc8a1-f4d6-4bf9-b58d-10cf32bfdbfc@www.fastmail.com> (raw)
In-Reply-To: <0bfaa5f2-558a-4109-a19f-de918eaef637@www.fastmail.com>
I guess one more thing that maybe worth investigating is Emacs + TRAMP. I've some experience with TRAMP and it mostly works. Trouble again is with this 2nd step:
> 2. `guix shell` or start a container, with entire system if I need to
Essentially TRAMP amounts to SSHing to your machine. But we want to be in that `guix shell` maybe even `guix shell -c` container, hell maybe even `guix system -c`. I can't even wrap my head around how that might work. TRAMP is basically talking to our SSHD started by current-system. I dunno but welcome suggestions, cause it'd be interesting to figure how that might work with TRAMP. Could be worth asking Emacs TRAMP mailing list, too.
Just thought I'd throw that idea out there, too. I would expect there to be a fair number of Emacs users among you.
next prev parent reply other threads:[~2022-03-22 23:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 14:09 Guix as remote dev machine t
2022-03-21 16:08 ` Brian Woodcox
2022-03-22 23:47 ` t
2022-03-22 23:54 ` t [this message]
2022-04-30 10:16 ` zimoun
2022-04-30 11:07 ` david larsson
2022-04-30 14:54 ` david larsson
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=644bc8a1-f4d6-4bf9-b58d-10cf32bfdbfc@www.fastmail.com \
--to=t@fullmeta.me \
--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).