From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list@redhat.com
Subject: Re: working with nano
Date: Wed, 14 Jun 2017 15:30:40 -0500 [thread overview]
Message-ID: <20170614153040.5862319b@bigbox.christie.dr> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1706141403090.3024@southernprince>
Tim here. Depending on the behavior you want, use one of the
following in your ~/.nanorc file.
If you want soft-wrapping where long lines display as wrapped but the
lines remain as individually long lines in the saved file, add
set softwrap
If you want hard-wrapping where it will automatically insert
line-breaks when you exceed the maximum line-length, you can
unset nowrap
(I find that double-negative is a bit weird). If it's doing that and
you *don't* want it to wrap, you can add
set nowrap
to your file.
Additionally, you can also specify where you want it to wrap, either
at a particular offset such as 75 characters per line:
set fill 75
or at an offset from your right-margin based on your screen-size,
such as
set fill -5
(the two commands should produce the same results on a standard
80-column terminal)
You should be able to read more about each of these options in
man nanorc
Hope this helps,
-tim
(for whom this is all a bit foreign since I'm a vi/vim/ed sorta guy
and only keep nano around for testing things just like this)
On June 14, 2017, Linux for blind general discussion wrote:
> Hi folks, Mark peveto here.
> Normally, seems I'd set this in my nanorc, but I can't find it.
> What i'm trying to do is make sure long line wrapping is on by
> default, so I don't hafta remember to hit alt l every time I start
> nano. There's a way to do it, but I dunno wha tit is. Can anyone
> help me out?
>
>
> Mark Peveto
> Registered Linux user number 600552
> Everything happens after coffee!
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion [this message]
Linux for blind general discussion
` Linux for blind general discussion
Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
Linux for blind general discussion
Linux for blind general discussion
` Linux for blind general discussion
Linux for blind general discussion
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=20170614153040.5862319b@bigbox.christie.dr \
--to=blinux-list@redhat.com \
/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.
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).