From: swedebugia <swedebugia@riseup.net>
To: t_w_@freenet.de, guix-devel@gnu.org
Subject: Re: Nano: disable hard wrapping by default
Date: Sun, 11 Nov 2018 09:02:43 +0100 [thread overview]
Message-ID: <fd4dc2a4-dee4-966f-4062-eeaa1a25034f@riseup.net> (raw)
In-Reply-To: <9d3f1901-c649-8966-ef42-30de5c5c5704@freenet.de>
On 2018-11-07 10:19, Thorsten Wilms wrote:
snip
> 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.
I can think of no such need. Could we add --disable-wrapping-as-root and
advise the user in the specification to create his own package inherited
from nano instead?
If a valid need does surface we can discuss changing the default.
> 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.
If I understand you correctly adding this as root would reenable the -w
behavior?
--
Cheers
Swedebugia
next prev parent reply other threads:[~2018-11-11 8:02 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 [this message]
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=fd4dc2a4-dee4-966f-4062-eeaa1a25034f@riseup.net \
--to=swedebugia@riseup.net \
--cc=guix-devel@gnu.org \
--cc=t_w_@freenet.de \
/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.