Hi,
> The point of "md" export back-end is not to provide the same features as
> full-fledged ones like "latex" or "html". I wrote it to take care of the
> boring stuff of markdown syntax. Anyone willing to write a back-end with
> a different Markdown flavour just needs to concentrate of the
> di
Hello,
Jay Kamat writes:
> I agree that vanilla markdown does not support title, but if ox-md does not
> support any form of title, then there is disparity between the output of other
> org exports and the markdown exporter. I would like to solve that disparity if
> possible.
The point of "md"
> I'm not so sure about it. Vanilla Markdown does not support title.
> Neither does "ox-md.el"
I agree that vanilla markdown does not support title, but if ox-md does not
support any form of title, then there is disparity between the output of other
org exports and the markdown exporter. I woul
On Thu, Aug 24, 2017, 5:31 AM Nicolas Goaziou
wrote:
>
> I'm not so sure about it. Vanilla Markdown does not support title.
> Neither does "ox-md.el"
>
Correct, vanilla Markdown does not support title. The file name is the
title.
For example, the file names of the Wiki pages on GitHub are rende
Hello,
Jay Kamat writes:
> The markdown editor should support TITLE
I'm not so sure about it. Vanilla Markdown does not support title.
Neither does "ox-md.el"
Is there any consensus about how title are handled in _vanilla_ syntax?
> -(defun org-md-template (contents _info)
> +(defun org-md-te
Hi!
Currently, the markdown org exporter does not export titles. For example, the
following org file:
#+TITLE: My Title
#+SUBTITLE: My Subtitle
#+OPTIONS: toc:nil
exports to an empty file. This patch adds title support to ox-md. Currently it
exports them as markdown headers. For example, the abo
