Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <wes@hardakers.net>
To: ding@gnus.org
Subject: text/plain with 80 char wrap vs the flowed mime-type (whatever it is)
Date: Wed, 27 Jan 2016 13:59:54 -0800	[thread overview]
Message-ID: <0legd2r8dh.fsf@wjh.hardakers.net> (raw)


So, I was co-writing a mail message with my wife yesterday and I noticed,
after sending her my copy of the proposed text, using the standard wrap
length (76 or whatever it is), that it looked fairly messed up on her
small phone screen.

What are people using for wrapping text these days?  Sticking with an
assumed 80 char screen?  Always using non-wrapped text?

Sadly, what I suspect I need to is set up different parameters in
different topics depending on who I'm writing to.

I suspect that the 80-char battle finally sunk with the massive change
in form factors that people read mail on now.  Should I bother to
continue assuming I know how I want to lay out my message, when the
reader really should have their preference for generic paragraphs (as
opposed to structured things like code or ascii diagrams).

Thoughts?

-- 
Wes Hardaker                                     
My Pictures:       http://capturedonearth.com/
My Thoughts:       http://blog.capturedonearth.com/



             reply	other threads:[~2016-01-27 21:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27 21:59 Wes Hardaker [this message]
2016-01-28  1:52 ` Jorge A. Alfaro-Murillo
2016-02-02 18:22   ` Wes Hardaker
2016-02-04  2:54   ` Mark Simpson
2016-02-04  5:18     ` Teemu Likonen
2016-02-04 14:30       ` Teemu Likonen
2016-02-05  0:21         ` Mark Simpson
2016-02-05 17:13     ` Jorge A. Alfaro-Murillo
2016-02-04 16:17   ` Nikolaus Rath
2016-02-04 22:41 Magnus Henoch
2016-02-05  0:14 ` Nikolaus Rath
2016-02-05  0:22 ` Mark Simpson

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=0legd2r8dh.fsf@wjh.hardakers.net \
    --to=wes@hardakers.net \
    --cc=ding@gnus.org \
    /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 NNTP newsgroup(s).