From: zimoun <zimon.toutoune@gmail.com>
To: t@fullmeta.me, help-guix@gnu.org
Subject: Re: Guix as remote dev machine
Date: Sat, 30 Apr 2022 12:16:19 +0200 [thread overview]
Message-ID: <86pmkyoozw.fsf@gmail.com> (raw)
In-Reply-To: <0bfaa5f2-558a-4109-a19f-de918eaef637@www.fastmail.com>
Hi,
On Mon, 21 Mar 2022 at 14:09, t@fullmeta.me wrote:
> I'm trying to come up with a reasonable way to use my Guix machine
> sitting in the attic as my remote development server. This presents
> several challenges. Locally I would typically follow these steps:
My workflow depends on my mood:
1. run emacs --daemon on the server; then inside xterm from my laptop,
connect via ssh and run emacsclient as tmux or screen would do.
2. run emacs with TRAMP via ssh to connect from my laptop to the
server.
3. run all from my laptop and offload the Guix builds to the server.
Cheers,
simon
next prev parent reply other threads:[~2022-04-30 10:19 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
2022-04-30 10:16 ` zimoun [this message]
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=86pmkyoozw.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=t@fullmeta.me \
/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).