From: Pierre Neidhardt <ambrevar@gmail.com>
To: Dan Partelly <dan_partelly@rdsor.ro>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Improving the README and new user experience
Date: Wed, 20 Jun 2018 09:20:54 +0200 [thread overview]
Message-ID: <87lgb9exex.fsf@gmail.com> (raw)
In-Reply-To: <7320F0B8-73A2-4E35-ADDE-D5E0E1E7E69A@rdsor.ro>
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
I think this would be a great addition to Guix.
I agree that for now Guix' learning curve is pretty steep. Even when
coming from rather barebone / Do-It-Yourself distributions like Gentoo /
Arch.
I'm not quite sure yet how to improve the experience to new users. I'd
need to install it several times, with other people and for different
scenarios before I can be a better judge.
I know some work is being done to add an installation helper program to
the install image.
Dan Partelly <dan_partelly@rdsor.ro> writes:
>> Also the editors included in the image are crap because they lack two important features: 1) keeping track of the damn paranteses and 2) comment and uncomment region.
>
> Yes. nano is crap. vi has paren matching, but doest keep tack of them . Editing lispy code with tracking of parens is not a pleasure.
Note that Guix also bundles Zile which is a tad better in my opinion.
Emacs would be Awesome but that would make the live image much heavier.
--
Pierre Neidhardt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-06-20 7:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 4:46 Improving the README and new user experience swedebugia
2018-06-20 6:13 ` Dan Partelly
2018-06-20 7:20 ` Pierre Neidhardt [this message]
2018-06-20 9:39 ` Dan Partelly
2018-06-24 14:02 ` Dan Partelly
2018-06-20 8:24 ` Danny Milosavljevic
2018-06-20 9:57 ` swedebugia
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=87lgb9exex.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=dan_partelly@rdsor.ro \
--cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).