From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id CC8946DE1034 for ; Fri, 11 Aug 2017 15:08:51 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -1.5 X-Spam-Level: X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5 tests=[AWL=-0.699, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id smfCKLxivSLu for ; Fri, 11 Aug 2017 15:08:51 -0700 (PDT) X-Greylist: delayed 363 seconds by postgrey-1.36 at arlo; Fri, 11 Aug 2017 15:08:50 PDT Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by arlo.cworth.org (Postfix) with ESMTPS id ECBA46DE100F for ; Fri, 11 Aug 2017 15:08:50 -0700 (PDT) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 520BE20F35; Fri, 11 Aug 2017 18:02:46 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Fri, 11 Aug 2017 18:02:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pnwbakers.com; h=cc:content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=doA9fNlb+PLOB+6C7qFpeKvudDysmNSlH8FP72 0xTwU=; b=j9K1RXdMn7OcstZmjFAuB52YKSUsFLjO0tt4AIFeNJgNPNb3syvcaz OK9AuCZFDKJrJ/Q5+2InaBUrs/U99sGQx3TPbKAPRTcf8WPgv7snO1ZFEpgBUeKf UUd0e3AvLoOMULaxvRlrBvm5Jb3lY+CQ0ei5LUpktECs8py7G5SVc= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=doA9fNlb+PLOB+6C7q FpeKvudDysmNSlH8FP720xTwU=; b=Fk7lQLnc/f8hbZKHxajEvlPHVKzYQjYRc0 3LpuyID6n4xeX5NKCuJjvnkBGC/oka3w5ITDbAaHuGshLcrioiP/fPgzJNS9izWs GYt2CGcY5fkMSFTkZdXxDcEqtQ7dGB2/WGEdrXEFerfu9RhF6mXfbAKuiYs8jW2G 5vQ1r0K0Xhh+aTvPEopJSjzcpbQZmmSLZ7a6H1Ed/rgclF7tAQGiGpksyy9N0v+G Qw4mQ4LHI7buK8PXVaVKtNy9Ulbvp8nXCFQ/bzw8Pad0Lwlyb3yt4GaT+WeOgYxG ERmcw+NsK4XOtCw3M17v1Hi0uA7PZ2pTAZGlP7XJCqpREwb9fCzg== X-ME-Sender: X-Sasl-enc: Dmc2Gowsr7FeDc7me86xqUStDr2oo8TBtwjoBReWJ/EV 1502488965 Received: from localhost (unknown [134.134.139.78]) by mail.messagingengine.com (Postfix) with ESMTPA id DE92B24775; Fri, 11 Aug 2017 18:02:45 -0400 (EDT) Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha256"; boundary="===============1272244227177368571==" MIME-Version: 1.0 Content-Disposition: inline To: Daniel Kahn Gillmor , Notmuch Mail From: Dylan Baker In-Reply-To: <87y3qqpvfz.fsf@fifthhorseman.net> Cc: Steve Kemp References: <87y3qqpvfz.fsf@fifthhorseman.net> Message-ID: <150248896497.16839.12866596405332768085@localhost.localdomain> User-Agent: alot/0.6.0dev Subject: Re: rendering and generating text/markdown parts Date: Fri, 11 Aug 2017 15:02:44 -0700 X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 22:08:51 -0000 --===============1272244227177368571== Content-Type: multipart/mixed; boundary="===============6219178863500276579==" MIME-Version: 1.0 --===============6219178863500276579== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable One of the alot devs here, Natively no. I have a fairly minor patch to alot that would make it work if= the type was text/markdown instead of text/plain. I have another patch that makes this render correctly as markdown, but it b= reaks lots of other text/plain emails that use characters in a way that they look= like markdown to cmark, but aren't actually markdown. I think if we're going to have a message format we should use text/markdown= or text/commonmark, or text/x-(markdown|commonmark) rather than text/plain as = the format. While it's safe to read markdown as plain text (it was originally u= sed that way anyway), it's not safe to assume that all text is valid markdown. elinks with "-dump-color-mode 1" did a pretty good job of formatting the ht= ml that came out of cmark. I've attached that if anyone wants to see it. Dylan Quoting Daniel Kahn Gillmor (2017-08-10 21:41:52) > Using `Content-Type: text/markdown` > ----------------------------------- > = > [Over on LWN, some discussion came up about rendering and generating > text/markdown variants of e-mails](https://lwn.net/Articles/730277/) > = > This is similar to (but maybe simpler than) [a proposal that was > discussed on the alot bug tracker earlier this > year](https://github.com/pazz/alot/issues/1051). > = > I thought i'd drop this mail as a marker for the start of a longer > discussion if anyone wants to try to take it further. > = > Next Steps > ---------- > = > I think this mail is (hopefully) actually composed correctly as > text/markdown. > = > Does anyone's MUA render it properly? Anyone want to post screenshots > or other renderings? > = > Anyone have suggestions about message composition in markdown? > = > --dkg >=20 --===============6219178863500276579== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="elinks-out.txt" Content-Disposition: attachment; filename="elinks-out.txt" =1B[0;30m=1B[0;37mUsing Content-Type: text/markdown = = =1B[0;37m = = =1B[0;37m =1B[0;34m[1]Over on LWN, some discussion came up about renderin= g and generating = =1B[0;34m=1B[0;37m =1B[0;34mtext/markdown variants of e-mails = = =1B[0;34m = = =1B[0;34m=1B[0;37m This is similar to (but maybe simpler than) =1B[0;34m[= 2]a proposal that was = =1B[0;34m=1B[0;37m =1B[0;34mdiscussed on the alot bug tracker earlier thi= s year=1B[0;37m. = =1B[0;37m = = =1B[0;37m I thought i'd drop this mail as a marker for the start of a lon= ger = =1B[0;37m discussion if anyone wants to try to take it further. = = =1B[0;37m = = =1B[0;37mNext Steps = = =1B[0;37m = = =1B[0;37m I think this mail is (hopefully) actually composed correctly as= = =1B[0;37m text/markdown. = = =1B[0;37m = = =1B[0;37m Does anyone's MUA render it properly? Anyone want to post scree= nshots or = =1B[0;37m other renderings? = = =1B[0;37m = = =1B[0;37m Anyone have suggestions about message composition in markdown? = = =1B[0;37m = = =1B[0;37m --dkg = = References Visible links 1. https://lwn.net/Articles/730277/ 2. https://github.com/pazz/alot/issues/1051 --===============6219178863500276579==-- --===============1272244227177368571== MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Description: signature Content-Type: application/pgp-signature; name="signature.asc"; charset="us-ascii" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEUwPMqo/+5aFHLzU4CJ4WlhQGiO8FAlmOKYQACgkQCJ4WlhQG iO98agf/aT1YWEGt5Rh2P0guPqzQuuNN9HxIapiTNybR0bTRZSliWjJk24VurZTP hKzrD0vA24e2dvFFAdjsc5aUjCr0kwShKKOPZ+IdJtnD1zARD512dqG0UU0ZL0xq GB0BXW2UIxJwheG4dcCLihYre48U/givbtvFNGn+REmimm1rIJ3UAcFDuP380cdU LkFgp1phvSO/cocEpe0MD8gsbIrokvXTUQfbkVgjSf0r6pU0Ass30UmMbUSyL4No PyDgReLjAnGxFhFu033pZpmkYmO/zIbXUIV9QGpb32ud5d5egzlBKzpApZMYq6AD fOknAhp11pRcZL3z3Pq4EtX2OwsyAw== =6FRy -----END PGP SIGNATURE----- --===============1272244227177368571==--