From: Dave Unger <dsunger@gmail.com>
To: supmua@googlegroups.com
Subject: Line wrapping and readability on mobile screens
Date: Sat, 18 Jul 2015 15:07:37 -0700 (PDT) [thread overview]
Message-ID: <5abfffcd-379f-414a-a450-bafa103fb991@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 684 bytes --]
I've noticed that the line breaks in emails that I send from Sup look bad
on mobile devices (or at least they look terrible on the gmail android
app). The problem seems to come from a collision between the hard
line-wraps that Vim inserts and the wrapping that the android client uses
to display the message (basically the default gmail client doesn't reflow
the paragraphs).
Is there something I can do on my end to send emails that other readers
(especially those more geared toward html messages) will have an easier
time displaying? I was playing around with just setting up vim for soft
wrapping, but I don't love that solution (for vim-based reasons).
Thanks,
Dave
[-- Attachment #1.2: Type: text/html, Size: 779 bytes --]
next reply other threads:[~2015-07-18 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 22:07 Dave Unger [this message]
2015-07-19 7:50 ` [sup] " Gaute Hope
2015-07-19 15:48 ` Dave Unger
2015-07-19 15:52 ` Gaute Hope
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=5abfffcd-379f-414a-a450-bafa103fb991@googlegroups.com \
--to=dsunger@gmail.com \
--cc=supmua@googlegroups.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