unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: myglc2 <myglc2@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: How about a 'guix-test-drive.scm'
Date: Mon, 01 Feb 2016 14:40:15 +0100	[thread overview]
Message-ID: <87powg5z28.fsf@gnu.org> (raw)
In-Reply-To: <874mdxzqor.fsf@gmail.com> (myglc2@gmail.com's message of "Thu, 28 Jan 2016 10:09:24 -0500")

myglc2 <myglc2@gmail.com> skribis:

> I installed guixSD on a headless server by cloning bare-bones.scm.  So
> far, this is a highly enjoyable ride, thank you!
>
> IMHO it would be better if bare-bones.scm did not set the SSH port to
> 2222, since this tripped me up, and I am guessing it might befuddle
> others.

Oh, I see.  This #:port-number thing was here mostly to show people how
to specify options, which I think is important, and I thought that
people would quickly notice the thing.  But I don’t know!

> Another suggestion: for someone like me wanting to test drive guix
> quickly, it would sure be helpful if there was a 'guix-test-drive.scm'
> that includes emacs, guile, and everything else needed to try and enjoy
> all the cool features described in the guix INFO pages and/or shown in
> the "The Emacs of Distros" video.
>
> Further, it might be good to have two versions ...
>
> - guix-test-drive-desktop.scm
>
> - guix-test-drive-headless-server.scm - emacs set to run over both tty
>   and X11
>
> In the meantime, does anyone have any bits and pieces of such a .scm
> they would care to share?

It seems to me that it’s just a matter of adding Emacs to the ‘packages’
field no?  Or did you have anything else in mind?

Thanks,
Ludo’.

  reply	other threads:[~2016-02-01 13:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 15:09 How about a 'guix-test-drive.scm' myglc2
2016-02-01 13:40 ` Ludovic Courtès [this message]
2016-03-08  1:47   ` myglc2

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=87powg5z28.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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).