unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: swedebugia <swedebugia@riseup.net>
To: Danny Milosavljevic <dannym@scratchpost.org>,
	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 11:57:53 +0200	[thread overview]
Message-ID: <F6DE1B89-60E3-4A1E-B6BC-90F4AA208D25@riseup.net> (raw)
In-Reply-To: <20180620102447.5992b459@scratchpost.org>



On June 20, 2018 10:24:47 AM GMT+02:00, Danny Milosavljevic <dannym@scratchpost.org> wrote:

... Snip

>Nano has paren matching (Alt-]) and commenting out (Alt-3).  It allows
>you to select text with cursor keys, then shift-cursor keys.
>
>It might make sense to patch the nano status line to mention that,
>though.
>
>I agree that otherwise it leaves something to be desired - but it can
>be used for editing lisp source code just fine.

That was news to me. Sounds good with a clarifying patch. 
Maybe the commenting out is just e making big changes and is is not needed for small incremental initial changes to the config. 
I will try to look into nano and see if I can figure out how to patch it. 

I think the manual should guide new users to a s little painful experience as possible. I will try building the installer and test it out as this would potentially take us a big step forward. 
-- 
Cheers Swedebugia

      reply	other threads:[~2018-06-20  9:58 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
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 [this message]

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=F6DE1B89-60E3-4A1E-B6BC-90F4AA208D25@riseup.net \
    --to=swedebugia@riseup.net \
    --cc=dan_partelly@rdsor.ro \
    --cc=dannym@scratchpost.org \
    --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).