First of all thank you for this.
I searched far and wide for a Markdown Viewer-only for some time now. There are but a few and almost all fall short of delivering the bare minimum acceptable functionality.
When I first embarked in that quest it seemed a fairly easy proposition: find an Markdown Reader- or Viewer-only for those files that are not to be edited because they represent a final, storable record of a Text-based work . Articles, essays and other writings authored by me or others that are not to be accidentally "corrupted" by me opening it in a Editor and, by mistake or lack of attention, unintentionally saving it with some edits (probably, I dare to venture it, this same rationale counted towards you own motivation to build this).
This is almost an Egg of Columbus kind of thing: pretty obvious in hindsight while not quite so much before. Or at least that is the most logical explanation I can summon for having found so few Viewers -- and of subpar quality -- while Editors (of increasingly good quality) seem to abound and prosper.
I was already contemplating rolling out my own when I, luckily, managed to serendipitously bump into mdview.
It does exactly what it says in the box (so to speak) and was quite elated when I tested with a handful of .md files I had just lying about.
However the feeling quickly subsided when I tried the Markdown files I described above (the final, non-editable, read-only ones), which, for convenience and to keep them visibly/clearly differentiated and differentiable from the others, have a different extension from the ones I mentioned in the title (which seem to be the only ones that trigger the rendering from the markup into the intended presentation format).
When I tried with those it only presented me back with the Text version of it (as if opened by any regular Text Editor/Viewer). Not the formatted one I was expecting and hoping for,
And so.
My request is: can you, please, kindly consider, in your next development cycle, to make this tool a more universal one, by giving more power and control back to the user -- by letting her/him decide which files can contain Markdown content (in other words, make it ignore the extension completely and try to render it as if the input was Markdown, regardless)?
Thank you so much.