From: Thorsten Wilms <t_w_@freenet.de>
To: guix-devel@gnu.org
Subject: Re: Nano: disable hard wrapping by default
Date: Wed, 7 Nov 2018 10:19:49 +0100 [thread overview]
Message-ID: <9d3f1901-c649-8966-ef42-30de5c5c5704@freenet.de> (raw)
In-Reply-To: <87h8gtv44k.fsf@gmail.com>
On 07/11/2018 06.38, Alex Vong wrote:
> To edit configuration files always pass nano the -w option. Without
> the -w option long lines become wrapped lines. This creates problems
> when saving because the lines are saved as wrapped lines instead of
> how they were in the original file. Many time this will break
> configuration files.
Even though I got in the habit of always using -w back in my Gentoo
days, I either never knew leaving it out would have affected more than
display, or I have forgotten about it. I think this qualifies as
unexpected/surprising behavior.
> I think we can also go ahead with the change if many nano users think it
> is a better default (even if not all distros do it).
Ubuntu is also in the --disable-wrapping-as-root flag club.
A potential reason against joining would be if there's a real need for
the default behavior (no --disable-wrapping-as-root, no -w) and it being
hard to achieve with the flag. It looks like the option to use would be:
-r number, --fill=number
Hard-wrap lines at column number. If this value is 0 or less, wrapping
will occur at the width of the screen less number columns, allowing the
wrap point to vary along with the width of the screen if the screen
is resized. The default value is -8. This option conflicts with -w
(--nowrap) -- the last one given takes effect.
--
Thorsten Wilms
thorwil's design for free software:
http://thorwil.wordpress.com/
next prev parent reply other threads:[~2018-11-07 9:22 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 [this message]
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
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=9d3f1901-c649-8966-ef42-30de5c5c5704@freenet.de \
--to=t_w_@freenet.de \
--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 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.