From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Radu Butoi Newsgroups: gmane.emacs.help Subject: Re: Sending mail: line wrapping and quoted-printable encoding Date: Mon, 27 Apr 2020 18:20:57 -0400 Message-ID: References: <87tv15ux8r.fsf@no.workgroup> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="79427"; mail-complaints-to="usenet@ciao.gmane.io" To: Gregor Zattler , help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Tue Apr 28 00:38:41 2020 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jTCOe-000KZI-RT for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 28 Apr 2020 00:38:40 +0200 Original-Received: from localhost ([::1]:35762 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jTCOd-0007tt-PB for geh-help-gnu-emacs@m.gmane-mx.org; Mon, 27 Apr 2020 18:38:39 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41990) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jTCOG-0007ti-Pt for help-gnu-emacs@gnu.org; Mon, 27 Apr 2020 18:38:17 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.90_1) (envelope-from ) id 1jTCOG-0007hQ-3E for help-gnu-emacs@gnu.org; Mon, 27 Apr 2020 18:38:16 -0400 Original-Received: from mail-qt1-x82a.google.com ([2607:f8b0:4864:20::82a]:38175) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jTCOF-0007hB-NE for help-gnu-emacs@gnu.org; Mon, 27 Apr 2020 18:38:15 -0400 Original-Received: by mail-qt1-x82a.google.com with SMTP id i68so15810579qtb.5 for ; Mon, 27 Apr 2020 15:38:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:in-reply-to:message-id:date:mime-version :content-transfer-encoding; bh=sIpmiz473CADkgcwkHCAXRXrVqS/ydVSapcc+MZHxCQ=; b=oqj1etijow+XwCXF9WJovkZFB5f+UlY2kBvKU6Ze6DhmHxS7kG7VnaN/mAU6zHemRq HlguL03icCOyDEeSeMRfaAQ5Rs9jV0m91zvIdXA+tmLGeNqZE8LGyGWnu0+5hP+cTP9S v0OmL5waMJRWsbh57IPXe6IYHbPtdrzGe5jaQR2QB9UM8Zv319PUYi5RYkOul6oMhU7X 8N4+RZe4pD2jTIHrJH+1jJJGUPUOoQA6A2eFpJYaO0ANsEsXcw2nqeMPBk7+an9sOIcD cpks70KXz5/1C7fSSEDQ3X7o5XNKQJkS0hvPFqbvTgVAalboSNRGbeKLZylKfT7vXSQi KH0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:in-reply-to:message-id:date :mime-version:content-transfer-encoding; bh=sIpmiz473CADkgcwkHCAXRXrVqS/ydVSapcc+MZHxCQ=; b=l+BYkigL4uE8HQmnKRZOMbOGOHNiIRpkVBcOUHre6X4tFsQSrB2sFQQqeGCy/cm0eU SKAHeW6obSsGY2VB8DlHYQPWkNn15PKK9BoGlcF/GA9QU5fV+s9PGqhCsAM+7ObZpnzL XbKTSviX6VMSb7ANicKTPgLaHxT6QfPbgxRE/ypowlSYwP//nH5mgUB9E/qlobttKnhB 02A8joRZz5xVTK/wF7HFWvVmcQ0c+qIWAtsCnwO3kUrNUuXYpY9jlJDm0aeG9EFjkZgD EGY5B2kpX3Ql8bAUhQnUQ8f5fGToG9q5zDWqCnTY1JYhxiT1/h+MnzZCX8Y8BV26mt99 0sGg== X-Gm-Message-State: AGi0PuaZnZM3d0HMTYZQpLCajJ41jD05rqVVaIVm3xbWd5bGuIFcG7AU d+XQAvsGyA43RSi5PZKRMcQ= X-Google-Smtp-Source: APiQypJkE9vRoPkDj/PleAtk/9BE67r6MbhJKN/NmL6wPw61Vak/yKjbLIWLS8hpLHlw3qF78zNo+w== X-Received: by 2002:ac8:758d:: with SMTP id s13mr25482695qtq.105.1588027094082; Mon, 27 Apr 2020 15:38:14 -0700 (PDT) Original-Received: from localhost ([2620:0:1003:321:28f5:a8b5:88d8:505b]) by smtp.gmail.com with ESMTPSA id v37sm12503162qtc.7.2020.04.27.15.38.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 27 Apr 2020 15:38:13 -0700 (PDT) In-Reply-To: <87tv15ux8r.fsf@no.workgroup> Received-SPF: pass client-ip=2607:f8b0:4864:20::82a; envelope-from=rbutoi@gmail.com; helo=mail-qt1-x82a.google.com X-detected-operating-system: by eggs.gnu.org: Error: [-] PROGRAM ABORT : Malformed IPv6 address (bad octet value). Location : parse_addr6(), p0f-client.c:67 X-Received-From: 2607:f8b0:4864:20::82a X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:122958 Archived-At: Hi Gregor, Gregor Zattler writes: > Hi Radu, emacs users, > * Radu Butoi [2020-04-26; 14:44]: >> Gregor Zattler writes: >>> * Radu Butoi [2020-04-25; 20:19]: >>>> I've recently set up my mail in Emacs, and it works >>>> well. Gmail, though, doesn't support [1] format=3Dflowed, >>>> resulting in the hard-to-read comb effect when viewing >>>> on mobile, which I'd like to avoid. Doing some more >>>> research, I see that the quoted-printable encoding >>>> (which Gmail does support [2], and I've confirmed) can >>>> also be used to avoid hard line breaks while keeping >>>> under the line length limit. >>> >>> actually I read the two resources you provided as gmail >>> displays format=3Dflowed formatted emails but does not >>> allow a web interface user to send such email. >>> >>> Sine you want to send emails with emacs everything should >>> be fine? >> >> It has worked in the past, but the redesign from ~two >> years ago removed it again. Apologies on the misleading >> link -- here's [1] some from more recently. I also >> confirmed it doesn't work. > > OK, but since the web page which states that Gmail wraps > quoted-printable encoded emails is even older than the ones > stating that Gmail does not wrap format=3Dflowed any more, > perhaps quoted-printable also will not work? > > And then there is the question who other providers will show > quoted-printable E-Mails in their clients (web interfaces). I appreciate your skepticism here :-) -- but from everything I've read the = quoted-printable encoding is well-supported by most/all email clients. It i= s from RFC2045 (MIME), whereas f=3Df is the lesser-supported RFC3676. Doing= a search of my maildir, I find a large majority of them contain it. To tes= t this, I'll be sending this message without hard-wrapping and with the Q-P= encoding. If it shows up fine, I think I need to `edebug` the Emacs MIME l= ibrary to find out exactly what's going wrong. > >>>> More generally, since I'm new to terminal-based email, >>>> what is the etiquette around hard-wrapping (or not)? >>>> Would it be rude to send paragraphs as one logical line >>>> (wrapped-in-transmission by quoted-printable) and expect >>>> people to soft-wrap? >>> >>> I send emails with lines no longer than 65 characters and >>> my mail client (notmuch/message/emacs) allows me to fill >>> the paragraphs while I type. >> >> Same here (notmuch), using the default message-fill-column >> of 72. I also set notmuch-wash-wrap-lines-length so that >> incoming long lines are wrapped. Is this a fair >> expectation to set on everyone? It's one of the first >> things I did, since I still get converted HTML mail that >> would otherwise take up the full width of my screen. >> >>> I assume today's smartphones to be more than capable of >>> showing 65 chars in one line. >> >> I'm afraid not: here's [2] how your email looks like on my >> Pixel 4 XL, a considerably big phone. > > thanks a lot for this screenshot. Obviously this also > depends on the users font size. I now re-wraped this whole > email to 60 chars per line and hope it displays well. Ah, there's no need to do that, since it is clearly Gmail who is at fault h= ere. Emacs is my main way or reading and writing mail, I'd just like to hav= e the option to use my phone. Thanks for your responses! And let me know if this shows up okay. =2DRadu