emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: ox-gfm and toc
Date: Fri, 21 Aug 2015 12:54:34 +0100	[thread overview]
Message-ID: <oluvbc8501x.fsf@med.uni-goettingen.de> (raw)

Hi all,

I am confused about how tables of content are handled in ox-gfm.


If I let org-mode do the default toc (#+OPTIONS: toc:t) then the TOC
seems to work -- even without using the generated anchors for the
headlines.

Test file:

--8<---------------cut here---------------start------------->8---
* Test File

With text.
--8<---------------cut here---------------end--------------->8---

exports to

--8<---------------cut here---------------start------------->8---


- [Test File](#test-file)

# Test File<a id="orgheadline1"></a>

With text.
--8<---------------cut here---------------end--------------->8---

This does not even use "orgheadline1".




If I disable the default TOC and include a TOC later via `#+TOC:
headlines 2` this toc is constructed in html and uses links to anchors.
But these anchors are not present in the md file anymore, so the TOC is
broken.

Test file:

--8<---------------cut here---------------start------------->8---
#+OPTIONS: toc:nil

#+TOC: headlines 2

* Test File

With text.
--8<---------------cut here---------------end--------------->8---

exports to

--8<---------------cut here---------------start------------->8---
<div id="table-of-contents">
<h2>Table of Contents</h2>
<div id="text-table-of-contents">
<ul>
<li><a href="#orgheadline1">1. Test File</a></li>
</ul>
</div>
</div>

# Test File

With text.
--8<---------------cut here---------------end--------------->8---

which refers to non-existent "orgheadline1".


Is this a bug in ox-gfm?

Best,
Andreas

                 reply	other threads:[~2015-08-21 11:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=oluvbc8501x.fsf@med.uni-goettingen.de \
    --to=andreas.leha@med.uni-goettingen.de \
    --cc=emacs-orgmode@gnu.org \
    /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).