From: Warren Young <warren@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 18:34:00 -0000 [thread overview]
Message-ID: <F9C557D1-1F61-4EB2-8A0C-7C89F5D1DD80@etr-usa.com> (raw)
In-Reply-To: <57ABF835.9050500@maxrnd.com>
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.
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.
Choosing not to insert hard breaks in paragraphs also allows me to post the too-common long modern URLs without using a shortener, so you can see where I intend for you to go before you click.
If your advice is to switch to a different mailer, there are only two others that have even slight appeal to me on this platform, and the maker of the first has repeatedly threatened to abandon its development, and the second costs more money than I believe the problem is worth. After all, *I* don’t have a problem with the status quo. So, do you want to buy me a software license to solve *your* problem? :)
next prev parent reply other threads:[~2016-08-11 18:34 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 [this message]
2016-08-11 20:44 ` Corinna Vinschen
2016-08-11 20:50 ` Warren Young
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=F9C557D1-1F61-4EB2-8A0C-7C89F5D1DD80@etr-usa.com \
--to=warren@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).