From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6172972915641810944 X-Received: by 10.112.9.100 with SMTP id y4mr11829472lba.20.1437292221533; Sun, 19 Jul 2015 00:50:21 -0700 (PDT) X-BeenThere: supmua@googlegroups.com Received: by 10.180.98.226 with SMTP id el2ls616032wib.45.gmail; Sun, 19 Jul 2015 00:50:19 -0700 (PDT) X-Received: by 10.194.2.169 with SMTP id 9mr12014006wjv.2.1437292219266; Sun, 19 Jul 2015 00:50:19 -0700 (PDT) Return-Path: Received: from mail-la0-f52.google.com (mail-la0-f52.google.com. [209.85.215.52]) by gmr-mx.google.com with ESMTPS id su3si602194lbb.1.2015.07.19.00.50.18 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 19 Jul 2015 00:50:18 -0700 (PDT) Received-SPF: neutral (google.com: 209.85.215.52 is neither permitted nor denied by best guess record for domain of eg@gaute.vetsj.com) client-ip=209.85.215.52; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 209.85.215.52 is neither permitted nor denied by best guess record for domain of eg@gaute.vetsj.com) smtp.mail=eg@gaute.vetsj.com Received: by laem6 with SMTP id m6so81266128lae.0 for ; Sun, 19 Jul 2015 00:50:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:subject:to:references:in-reply-to :user-agent:message-id:mime-version:content-type :content-transfer-encoding; bh=jYveG2BDxsAh3k0lzvn5KgmYIsNK1cjVOpf9vVc8WtE=; b=LCgO/SG1wBkinsiRZBlKP2fgBo0jHOfqzivftA29Tj3SbKMcYQxfkNFy5NCf4w1ilh o9OmHUhlHtCrw9rNlVFjeofoeDIER324g4DpQpFrPStGxoiJxaa/gNQnZ0KT3o9vCCVl MAJc1LzCD9qSezf6NkPvIMcSJqRo2JyA28aDRgYQnoebYtCoNepnkF3TM5v9VI59+qxM OcN1396kmGwzxBjtHbZuj3j06as9D4kzOb3HYP5QeS89fyt5BnY+xfLLl0/OgN56TBIq lZXfLprwYOGD1isEi7o80hBjJsaLewrbIih2DDd2nCqVAFGKLBtbBdJi7RAsJN8Kprio COXw== X-Gm-Message-State: ALoCoQkwNelX3y4ZdIVGO/eqhTu8WFyrkkO0xXGK0Lp/uVNQ4gKC92z95QFGVPezb7k2l58lkbRO X-Received: by 10.153.4.40 with SMTP id cb8mr21669863lad.39.1437292218662; Sun, 19 Jul 2015 00:50:18 -0700 (PDT) Return-Path: Received: from localhost (c6878BF51.dhcp.as2116.net. [81.191.120.104]) by smtp.gmail.com with ESMTPSA id k9sm4271677lbp.13.2015.07.19.00.50.17 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 19 Jul 2015 00:50:17 -0700 (PDT) Date: Sun, 19 Jul 2015 07:50:16 +0000 From: Gaute Hope Subject: Re: [sup] Line wrapping and readability on mobile screens To: Dave Unger , supmua@googlegroups.com References: <5abfffcd-379f-414a-a450-bafa103fb991@googlegroups.com> In-Reply-To: <5abfffcd-379f-414a-a450-bafa103fb991@googlegroups.com> User-Agent: astroid/vv0.3-35-g5b47250d (https://github.com/gauteh/astroid) Message-Id: <1437292139-astroid-0-yfsqqwnl9d-1954@strange> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Dave Unger writes on July 19, 2015 0:07: > I've noticed that the line breaks in emails that I send from Sup look bad= =20 > on mobile devices (or at least they look terrible on the gmail android=20 > app). The problem seems to come from a collision between the hard=20 > line-wraps that Vim inserts and the wrapping that the android client uses= =20 > to display the message (basically the default gmail client doesn't reflow= =20 > the paragraphs).=20 >=20 > Is there something I can do on my end to send emails that other readers=20 > (especially those more geared toward html messages) will have an easier=20 > time displaying? I was playing around with just setting up vim for soft=20 > wrapping, but I don't love that solution (for vim-based reasons).=20 >=20 > Thanks, > Dave >=20 This could be related to format-flowed, which is not set to true in sup. Check out this old PR: https://github.com/sup-heliotrope/sup/pull/228 -gaute =