unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Dylan Baker <dylan@pnwbakers.com>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	Notmuch Mail <notmuch@notmuchmail.org>
Cc: Steve Kemp <steve@steve.org.uk>
Subject: Re: rendering and generating text/markdown parts
Date: Fri, 11 Aug 2017 15:02:44 -0700	[thread overview]
Message-ID: <150248896497.16839.12866596405332768085@localhost.localdomain> (raw)
In-Reply-To: <87y3qqpvfz.fsf@fifthhorseman.net>


[-- Attachment #1.1: Type: text/plain, Size: 1758 bytes --]

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 breaks
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 used
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 html 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
> 

[-- Attachment #1.2: elinks-out.txt --]
[-- Type: text/plain, Size: 2143 bytes --]

^[[0;30m^[[0;37mUsing Content-Type: text/markdown                                               
^[[0;37m                                                                                
^[[0;37m   ^[[0;34m[1]Over on LWN, some discussion came up about rendering and generating       
^[[0;34m^[[0;37m   ^[[0;34mtext/markdown variants of e-mails                                            
^[[0;34m                                                                                
^[[0;34m^[[0;37m   This is similar to (but maybe simpler than) ^[[0;34m[2]a proposal that was           
^[[0;34m^[[0;37m   ^[[0;34mdiscussed on the alot bug tracker earlier this year^[[0;37m.                         
^[[0;37m                                                                                
^[[0;37m   I thought i'd drop this mail as a marker for the start of a longer           
^[[0;37m   discussion if anyone wants to try to take it further.                        
^[[0;37m                                                                                
^[[0;37mNext Steps                                                                      
^[[0;37m                                                                                
^[[0;37m   I think this mail is (hopefully) actually composed correctly as              
^[[0;37m   text/markdown.                                                               
^[[0;37m                                                                                
^[[0;37m   Does anyone's MUA render it properly? Anyone want to post screenshots or     
^[[0;37m   other renderings?                                                            
^[[0;37m                                                                                
^[[0;37m   Anyone have suggestions about message composition in markdown?               
^[[0;37m                                                                                
^[[0;37m        --dkg                                                                   

References

   Visible links
   1. https://lwn.net/Articles/730277/
   2. https://github.com/pazz/alot/issues/1051

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

-----BEGIN PGP SIGNATURE-----

iQEzBAABCAAdFiEEUwPMqo/+5aFHLzU4CJ4WlhQGiO8FAlmOKYQACgkQCJ4WlhQG
iO98agf/aT1YWEGt5Rh2P0guPqzQuuNN9HxIapiTNybR0bTRZSliWjJk24VurZTP
hKzrD0vA24e2dvFFAdjsc5aUjCr0kwShKKOPZ+IdJtnD1zARD512dqG0UU0ZL0xq
GB0BXW2UIxJwheG4dcCLihYre48U/givbtvFNGn+REmimm1rIJ3UAcFDuP380cdU
LkFgp1phvSO/cocEpe0MD8gsbIrokvXTUQfbkVgjSf0r6pU0Ass30UmMbUSyL4No
PyDgReLjAnGxFhFu033pZpmkYmO/zIbXUIV9QGpb32ud5d5egzlBKzpApZMYq6AD
fOknAhp11pRcZL3z3Pq4EtX2OwsyAw==
=6FRy
-----END PGP SIGNATURE-----

  reply	other threads:[~2017-08-11 22:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-11  4:41 rendering and generating text/markdown parts Daniel Kahn Gillmor
2017-08-11 22:02 ` Dylan Baker [this message]
2017-08-11 23:05   ` Daniel Kahn Gillmor
2017-08-11 23:36     ` Dylan Baker

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

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=150248896497.16839.12866596405332768085@localhost.localdomain \
    --to=dylan@pnwbakers.com \
    --cc=dkg@fifthhorseman.net \
    --cc=notmuch@notmuchmail.org \
    --cc=steve@steve.org.uk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

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 read-only IMAP folder(s) and NNTP newsgroup(s).