Rasmus writes:
> Josiah Schwab writes:
>> Independent of the confusion it caused me while trying to figure out how
>> things work, it seems strange that the ox-md exporter generates a
>> non-markdown TOC using org-html-toc. But I will leave that for those
>> who really use the markdown exporte
Josiah Schwab writes:
> Rasmus writes:
>
>> Josiah Schwab writes:
>>
>>> How does one go about overriding org-html-toc, which unlike something
>>> like org-html-bold, does not appear in org-export-define-backend? I
>>> don't want the TOC not to appear, rather want it to be generated by
>>> anoth
Rasmus writes:
> Josiah Schwab writes:
>
>> How does one go about overriding org-html-toc, which unlike something
>> like org-html-bold, does not appear in org-export-define-backend? I
>> don't want the TOC not to appear, rather want it to be generated by
>> another function, org-md-toc or what
Hi Josiah,
Josiah Schwab writes:
> How does one go about overriding org-html-toc, which unlike something
> like org-html-bold, does not appear in org-export-define-backend? I
> don't want the TOC not to appear, rather want it to be generated by
> another function, org-md-toc or what have you.
Hi All,
I'm working on writing a derived exporter and I've been using ox-md.el
as a template/guide.
If I use the markdown exporter to export the following org file
* Meeting Notes
** First Topic
*** Subtopic 1
+ a point
+ an *important* point
*** Subtopic 2
+ another point
+ an /interesting/ poi
