From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Adam Sjøgren via info-gnus-english" <info-gnus-english@gnu.org>
Cc: "Adam Sjøgren" <asjo@koldfront.dk>
Subject: Re: Rendering Content-Type: text/markdown with shr via text/html?
Date: Sat, 03 Aug 2019 14:22:57 +0200 [thread overview]
Message-ID: <87mugqjv4u.fsf@mouse.gnus.org> (raw)
In-Reply-To: <87h86zdvkr.fsf@tullinup.koldfront.dk> ("Adam =?utf-8?Q?Sj?= =?utf-8?Q?=C3=B8gren?= via info-gnus-english"'s message of "Sat, 03 Aug 2019 00:57:40 +0200")
Adam Sjøgren via info-gnus-english <info-gnus-english@gnu.org> writes:
> I'm experimenting with posting articles with text/markdown as the
> Content-Type.
>
> I was wondering what the easiest way is to have Gnus translate such
> articles to HTML and display them via shr, as is done for text/html
> articles.
>
> Anyone already tackled this?
I don't think so. There's several markdown packages on Marmalade, but
these seem more geared towards generating Markdown, and not displaying
it.
A function to convert Markdown into HTML might be nice, but I haven't
really seen anybody post with Markdown, so I'm not sure how useful this
would be. But I guess it's a chicken and egg problem -- if mail readers
did support rendering Markdown, then people would start writing in
Markdown.
But is that a good thing? :-)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2019-08-03 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 22:57 Adam Sjøgren via info-gnus-english
2019-08-03 12:22 ` Lars Ingebrigtsen [this message]
2019-08-03 12:32 ` Adam Sjøgren via info-gnus-english
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=87mugqjv4u.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=asjo@koldfront.dk \
--cc=info-gnus-english@gnu.org \
/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;
as well as URLs for NNTP newsgroup(s).