I'm the author of Markdown Here. And surprised to open HN and see it on the first page! I can answer any questions (although it's really a straightforward tool -- it does what it says on the box).
It suffers from a number of security issues [1] and it's unmaintained (or at least the maintainer is AWOL and without him new releases can't be tagged).
Why did you use marked instead of markdown-it or another CommonMark-compatible parser? Have you thought about switching to a library which supports more features?
Markdown Here predates both CommonMark and markdown-it by a couple of years. marked.js was the best choice when I created MDH. That being said, I have started work on switching to markdown-it (see comment above).
Hi Adam! I installed Markdown Here from the Chrome Web Store, and I noticed it installed 2.12.0. However, it looks like you released 2.13.1 on GitHub. Should I be installing from GitHub?
2.13.1 and .2 are Mozilla-specific releases, to deal with the change from XUL to WebExtensions in Firefox, while still supporting Thunderbird (and Postbox) and old Firefox (and Palemoon). I'll cut a release soon-ish to fix a couple of bugs:
https://github.com/adam-p/markdown-here/blob/master/src/comm...
I can't tell if you're kidding, but... Markdown Here gives you control over the CSS used when rendering, so you can put those loud styles on, say, H1, and then just write:
that... just... that doesn't make sense. why would you use a plugin that converts markdown to html in browser windows to do automated sending. There have been command line tools to convert markdown to html since the beginning (literally, first implementation by gruber). Pandoc is probably the go-to one these days but yeah, that's just.... not the right tool for the job.
