public inbox for
 help / color / mirror / Atom feed
From: Corinna Vinschen <>
Subject: Re: First experiences with WSL (a.k.a. Bash on Windows)
Date: Thu, 11 Aug 2016 20:44:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1484 bytes --]

On Aug 11 12:34, Warren Young wrote:
> On Aug 10, 2016, at 9:59 PM, Mark Geisert <> wrote:
> > 
> > Warren Young wrote:
> > [...]
> > 
> > Would you kindly ?
> That option doesn’t exist in this program.

It does in any program.  Just enter your LF manually.  It's not
complicated, I do this in vim all the time to keep the linelength in

There's also which asks for a max
line length of 65.  Yes, I don't follow this exactly either, I'm using a
max. linelength of 72 typically, but at least I *do* add my LFs
manually, out of courtesy to my readers.

And yes, there are still folks out there using text-only MUAs like mutt
in an 80 columns terminal.  I do.

> 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.
To be able to add a comment after a single sentence, one has to manually
break your lines for you from inside the editor.

So instead of just using linebreaks out of courtesy to allow others to
comment on your mails easily, you push the onus on the recipient.

Bottom line is, it just isn't fun to reply to those mails, so I do it
less and less often.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-08-11 20:44 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 [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).