From: Warren Young <wyml@etr-usa.com>
To: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk@cygwin.com>
Subject: Re: First experiences with WSL (a.k.a. Bash on Windows)
Date: Thu, 11 Aug 2016 20:50:00 -0000 [thread overview]
Message-ID: <FDB0837E-7FF5-422A-9176-66222EEF091F@etr-usa.com> (raw)
In-Reply-To: <20160811204403.bvdlnvwt26o7fmnn@calimero.vinschen.de>
On Aug 11, 2016, at 2:44 PM, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
>
> On Aug 11 12:34, Warren Young wrote:
>> On Aug 10, 2016, at 9:59 PM, Mark Geisert <mark@maxrnd.com> wrote:
>>>
>>> Warren Young wrote:
>>> [...]
>>>
>>> Would you kindly https://cygwin.com/acronyms/#PCYMTWLL ?
>>
>> That option doesn’t exist in this program.
>
> It does in any program. Just enter your LF manually.
Seriously? In 2016?
> And yes, there are still folks out there using text-only MUAs like mutt
> in an 80 columns terminal. I do.
http://www.rdrop.com/docs/mutt/manual330.html
>> I don’t see the problem anyway. One unbroken line per paragraph is trivial to wrap in software, and then you get breaks where *you* like them, rather than where *I* like them.
>
> You're lucky. You never had to reply to your own mails. I do and it's
> seriously ugly to see and edit mails with extremly long lines in vim.
Add this to your .vimrc:
map <F2> !}fmt -w72<CR>
Problem solved.
next prev parent reply other threads:[~2016-08-11 20:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 9:57 Warren Young
2016-08-11 4:00 ` Mark Geisert
2016-08-11 18:34 ` Warren Young
2016-08-11 20:44 ` Corinna Vinschen
2016-08-11 20:50 ` Warren Young [this message]
2016-08-11 21:06 ` Corinna Vinschen
2016-08-11 23:08 ` Herbert Stocker
2016-08-12 6:22 ` Mark Geisert
2016-08-17 0:53 ` Robert Pendell
2016-08-11 18:36 ` Warren Young
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=FDB0837E-7FF5-422A-9176-66222EEF091F@etr-usa.com \
--to=wyml@etr-usa.com \
--cc=cygwin-talk@cygwin.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).