all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: swedebugia <swedebugia@riseup.net>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Nano: disable hard wrapping by default
Date: Sun, 11 Nov 2018 09:04:17 +0100	[thread overview]
Message-ID: <57fa27a8-3301-2d96-ed75-81e0671a1494@riseup.net> (raw)
In-Reply-To: <20181107182024.GA14925@jasmine.lan>

On 2018-11-07 19:20, Leo Famulari wrote:

snip

> In general, we don't change upstream defaults in Guix except when it's
> required for portability or to fix really egregious problems (i.e.
> security bugs). This is different from distros like Debian that
> basically fork the software and make a huge number of changes to suit
> the package maintainer's taste.
> 
> This keeps package maintenance relatively easy for us and ensures that
> important changes get pushed upstream so that all users can benefit.
> 
> Having said that, this line wrapping thing is a very bad default, and I
> think we should change it. Nano is one of the editors in the GuixSD
> installer. It needs to be easy to use.
> 
> If we change the default in our package, we need to file a bug upstream:
> 
> https://savannah.gnu.org/bugs/?group=nano
> 

Agreed. :)

-- 
Cheers
Swedebugia

  reply	other threads:[~2018-11-11  8:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06 18:43 Nano: disable hard wrapping by default swedebugia
2018-11-06 18:49 ` swedebugia
2018-11-06 19:27   ` Alex Vong
2018-11-06 21:57     ` swedebugia
2018-11-07  5:38       ` Alex Vong
2018-11-07  9:19         ` Thorsten Wilms
2018-11-11  8:02           ` swedebugia
2018-11-11 10:16             ` Thorsten Wilms
2018-11-07 18:20 ` Leo Famulari
2018-11-11  8:04   ` swedebugia [this message]
2018-11-15 13:14     ` swedebugia
2018-11-15 20:28       ` Alex Vong
2019-03-25 19:08 ` Leo Famulari

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57fa27a8-3301-2d96-ed75-81e0671a1494@riseup.net \
    --to=swedebugia@riseup.net \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.