emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: jschwab@gmail.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Customizing TOCs in Derived Exporters
Date: Thu, 19 Sep 2013 00:12:49 +0200	[thread overview]
Message-ID: <87y56tsrry.fsf@gmx.us> (raw)
In-Reply-To: <87a9j9esq9.fsf@gmail.com> (Josiah Schwab's message of "Wed, 18 Sep 2013 14:15:58 -0700")

Josiah Schwab <jschwab@gmail.com> 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
>>> another function, org-md-toc or what have you.
>>
>> I'm not sure whether this would work with md simply 'cause I haven't
>> worked with the html+friends exporter(s), but perhaps you could
>> replace the inner-template, i.e. write a replacement for
>> org-html-inner-template.
>
> Yes, this suggestion worked for me.  Thank you for the advice.  Little
> by little I will come to understand the new exporter (not that I
> understood the old one).
>
> 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 exporter, which is neither you or me.

Is there a vanilla-markdown TOC-keyword?  My understanding is that
markdown always understand plain html, whence the html-toc is
reusable.  If there is exists a vanilla-markdown TOC perhaps it should
be used.

–Rasmus

-- 
Dung makes an excellent fertilizer

  reply	other threads:[~2013-09-18 22:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-16 20:11 Customizing TOCs in Derived Exporters Josiah Schwab
2013-09-17 13:49 ` Rasmus
2013-09-18 21:15   ` Josiah Schwab
2013-09-18 22:12     ` Rasmus [this message]
2013-09-18 22:53       ` Josiah Schwab

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y56tsrry.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=emacs-orgmode@gnu.org \
    --cc=jschwab@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).