public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Piero Grandesso <piero.tasso-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: table-of-contents vs toc behavior
Date: Thu, 2 Nov 2017 15:38:14 +0100	[thread overview]
Message-ID: <CAFMWPddryEf+8MoV6fCS84se871We6nx1q+cp=9L2gn3eMT=Dw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]

Hi all,

I have some problems understanding the correct behavior of the variables
--toc and --table-of-contents.

As per this commit[1] I would expect that I could enable the generation of
the table of contents by simply inserting `toc: true` in my YAML metadata
block; the table of contents should then appear in my template when invoked
by `$table-of-contents$`. Is it correct or did I misunderstood something?

If that is the desired behavior, than I think there could be a bug:

with `toc: true` specified in my example.md, the following command will
produce an HTML file with an empty <nav> block:

pandoc example.md -s -o example.html


to obtain a working table of contents I have to specify --toc:

pandoc example.md --toc -s -o example.html


I am working with pandoc on linux, pandoc -v:

pandoc 2.0.1
Compiled with pandoc-types 1.17.2, texmath 0.9.4.4, skylighting 0.4.2


Thanks,
Piero


[1]:
https://github.com/jgm/pandoc/commit/75f4e41d7d292e011a83d06efebc356060ea812b

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CAFMWPddryEf%2B8MoV6fCS84se871We6nx1q%2Bcp%3D9L2gn3eMT%3DDw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 2528 bytes --]

             reply	other threads:[~2017-11-02 14:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02 14:38 Piero Grandesso [this message]
     [not found] ` <CAFMWPddryEf+8MoV6fCS84se871We6nx1q+cp=9L2gn3eMT=Dw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-02 19:27   ` John MACFARLANE
2017-11-03 11:01     ` Piero Grandesso
     [not found]       ` <afe3b9e2-d7b7-45e7-87d6-422b9dd5a378-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-03 16:40         ` John MACFARLANE

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

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

  git send-email \
    --in-reply-to='CAFMWPddryEf+8MoV6fCS84se871We6nx1q+cp=9L2gn3eMT=Dw@mail.gmail.com' \
    --to=piero.tasso-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).