unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
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 10:24:47 +0200	[thread overview]
Message-ID: <20180620102447.5992b459@scratchpost.org> (raw)
In-Reply-To: <7320F0B8-73A2-4E35-ADDE-D5E0E1E7E69A@rdsor.ro>

[-- Attachment #1: Type: text/plain, Size: 646 bytes --]

>>  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. 

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.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2018-06-20  8:25 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 [this message]
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=20180620102447.5992b459@scratchpost.org \
    --to=dannym@scratchpost.org \
    --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).