public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Duplicate TOC entries
Date: Thu, 10 Nov 2022 15:59:33 -0800	[thread overview]
Message-ID: <DB0608E9-A288-4299-832D-9B81C03A042F@gmail.com> (raw)
In-Reply-To: <7713e9c1-1056-4891-996b-1297e2145913n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Try removing the filters to rule that out.

Then try without the custom template.

> On Nov 10, 2022, at 2:56 PM, Emil Tywoniak <emil.tywoniak-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> 
> Hello everybody,
> I'm building a pdf with a latex template, and every single entry in the TOC as well as the .toc file is duplicated likle this:
> 
> \contentsline {section}{Verification}{11}{section*.20}%
> \contentsline {section}{Verification}{11}{section*.20}%
> 
> I'm absolutely stumped, I would like to untangle pandoc's and latexmk's invocations to at least know what source code to read but I can't figure that out. The repository is at https://gitlab.com/tywonemi-school-stuff/titania/doc and you need latexmk, inkscape, and this latex template/cls to build it. If it helps, here's what the Makefile runs:
> 
> pandoc analysis.md \
> -s \
> --filter pandoc-minted/pandoc-minted.py \
> --filter pandoc-svg/pandoc-svg.py \
> --data-dir=. \
> --template=ctuthesis.tex \
> --bibliography bibliography.bib \
> --pdf-engine=latexmk \
> --pdf-engine-opt=-outdir=temp \
> --pdf-engine-opt=-shell-escape \
> --pdf-engine-opt=-bibtex \
> -o doc.pdf
> 
> If I let it generate .tex, it has sections looking as expected:
> 
> \hypertarget{verification}{%
> \section{Verification}\label{verification}}
> 
> Any suggestions where to look would be much appreciated. I found zero cases of somebody's .toc items being duplicated and zero information on how the .toc is even generated.
> 
> Thanks,
> Emil J
> 
> -- 
> 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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/7713e9c1-1056-4891-996b-1297e2145913n%40googlegroups.com.

-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/DB0608E9-A288-4299-832D-9B81C03A042F%40gmail.com.


      parent reply	other threads:[~2022-11-10 23:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 22:56 Emil Tywoniak
     [not found] ` <7713e9c1-1056-4891-996b-1297e2145913n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-10 23:59   ` John MacFarlane [this message]

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=DB0608E9-A288-4299-832D-9B81C03A042F@gmail.com \
    --to=fiddlosopher-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).