public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: A A <amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: pandoc-crossref not playing nice with header includes
Date: Tue, 7 Mar 2023 14:06:17 +0100	[thread overview]
Message-ID: <CAMwawgMDb2ZF9i8T5sxeFqrnf3RRh+thSJXyxPsufFqPC4czBQ@mail.gmail.com> (raw)
In-Reply-To: <ZAcdDn+j/f55E9xQ@localhost>

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

You can include it in an external metadata file referred to via the
—metadata-file option

I believe that would still be a YAML file with weird syntax like this?

header-includes:
- |
  ~~~{=latex}
  \let\oldsection\section
  \renewcommand{\section}[1]{\clearpage\oldsection{#1}}
  ~~~

If so then yes, I definitely prefer doing my own header.tex. But this would
have to include all the content necessary for pandoc-crossref to work
properly. Any ideas where I could find this content? I briefly skimmed the
pandoc-crossref repo but didn’t find anything obvious…

On Tue, 7 Mar 2023 at 12:16, Bastien DUMONT <bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org>
wrote:

> You can include it in an external metadata file referred to via the
> --metadata-file option. However, if you customize the LaTeX preamble
> heavily, it may be preferable to use a custom template including the
> content of header.tex.
>
> Le Tuesday 07 March 2023 à 12:07:19PM, A A a écrit :
> > That would force me to put my header content within my markdown file and
> remove
> > "header.tex" completely. I would very much prefer to keep them as
> separate
> > files.
> >
> > The header.tex for my use case ia much more involved. Including it
> inside the
> > markdowm YAML block like that would be quite ugly IMO.
> >
> >
> >
> >
> >
> > On Tue, 7 Mar 2023, 10:16 Bastien DUMONT, <[1]bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org>
> wrote:
> >
> >     Since you don't use a custom template, you don't have to add $for
> >     (header-includes)$ etc. anywhere: it is already included in the
> default
> >     LaTeX template.
> >     The answer for your use case is here: [2]
> https://github.com/lierdakil/
> >     pandoc-crossref/issues/47#issuecomment-614404532
> >
> >     Le Tuesday 07 March 2023 à 10:02:38AM, A A a écrit :
> >     > Files
> >     >
> >     > test.py
> >     >
> >     > def f(x):
> >     >     return x
> >     >
> >     > test.md
> >     >
> >     > ~~~{
> >     >   #lst:test
> >     >   .py
> >     >   include="test.py"
> >     >   caption=`test.py`
> >     > }
> >     > ~~~
> >     >
> >     > header.tex
> >     >
> >     > \usepackage{minted}
> >     >
> >     > \definecolor{bg}{rgb}{0.85, 0.85. 0.85}
> >     > \setminted{breaklines=true, bgcolor=bg, breakanywhere}
> >     >
> >     > Compilation
> >     >
> >     > I’m compiling with:
> >     >
> >     > pandoc -s -F pandoc-crossref -L include-code-files.lua -L
> minted.lua -H
> >     header.tex --from markdown --to latex test.md -o test.tex
> >     > latexmk --shell-escape -pdflatex test.tex
> >     >
> >     > I get an error upon compilation, because pandoc-crossref defines
> its own
> >     header
> >     > include which gets overwritten by my -H header.tex. This [1]link
> provides
> >     more
> >     > information.
> >     >
> >     > I tried the solution proposed by @lierdakil in the link provided
> but get
> >     an
> >     > error:
> >     >
> >     >     ! LaTeX Error: Missing \begin{document}.
> >     >
> >     >     See the LaTeX manual or LaTeX Companion for explanation.
> >     >     Type H for immediate help.
> >     >
> >     >     l.97 $
> >     >     for(header-includes)$
> >     >     ?
> >     >
> >     > So I’m at a bit of a loss regarding what to do here, Any pointers
> >     welcome.
> >     > Thanks
> >     >
> >     > --
> >     > 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 [2][3]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> >     > To view this discussion on the web visit [3][4]
> https://groups.google.com/
> >     d/msgid/
> >     > pandoc-discuss/
> >     > CAMwawgPTeNSdJ7FDbc9tmw8ax06K7n_uGxvB-mCn2fvBzdD%3DUg%[5]
> 40mail.gmail.com
> >     .
> >     >
> >     > References:
> >     >
> >     > [1] [6]https://github.com/lierdakil/pandoc-crossref/issues/47
> >     > [2] mailto:[7]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> >     > [3] [8]https://groups.google.com/d/msgid/pandoc-discuss/
> >     CAMwawgPTeNSdJ7FDbc9tmw8ax06K7n_uGxvB-mCn2fvBzdD%3DUg%
> 40mail.gmail.com?
> >     utm_medium=email&utm_source=footer
> >
> >     --
> >     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 [9]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> >     To view this discussion on the web visit [10]
> https://groups.google.com/d/
> >     msgid/pandoc-discuss/ZAcA4dThsf/pAK2e%40localhost.
> >
> > --
> > 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 [11]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit [12]
> https://groups.google.com/d/msgid/
> > pandoc-discuss/
> > CAMwawgNJcw9d-aMSPFStx%2BwU__GrsDVhhNrARCLf4CdHNiGCWA%40mail.gmail.com.
> >
> > References:
> >
> > [1] mailto:bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org
> > [2]
> https://github.com/lierdakil/pandoc-crossref/issues/47#issuecomment-614404532
> > [3] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > [4] https://groups.google.com/d/msgid/
> > [5] http://40mail.gmail.com/
> > [6] https://github.com/lierdakil/pandoc-crossref/issues/47
> > [7] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > [8]
> https://groups.google.com/d/msgid/pandoc-discuss/CAMwawgPTeNSdJ7FDbc9tmw8ax06K7n_uGxvB-mCn2fvBzdD%3DUg%40mail.gmail.com?utm_medium=email&utm_source=footer
> > [9] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > [10]
> https://groups.google.com/d/msgid/pandoc-discuss/ZAcA4dThsf/pAK2e%40localhost
> > [11] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > [12]
> https://groups.google.com/d/msgid/pandoc-discuss/CAMwawgNJcw9d-aMSPFStx%2BwU__GrsDVhhNrARCLf4CdHNiGCWA%40mail.gmail.com?utm_medium=email&utm_source=footer
>
> --
> 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/ZAcdDn%2Bj/f55E9xQ%40localhost
> .
>

-- 
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/CAMwawgMDb2ZF9i8T5sxeFqrnf3RRh%2BthSJXyxPsufFqPC4czBQ%40mail.gmail.com.

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

  reply	other threads:[~2023-03-07 13:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07  9:02 A A
     [not found] ` <CAMwawgPTeNSdJ7FDbc9tmw8ax06K7n_uGxvB-mCn2fvBzdD=Ug-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-03-07  9:16   ` Bastien DUMONT
2023-03-07 11:07     ` A A
     [not found]       ` <CAMwawgNJcw9d-aMSPFStx+wU__GrsDVhhNrARCLf4CdHNiGCWA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-03-07 11:16         ` Bastien DUMONT
2023-03-07 13:06           ` A A [this message]
     [not found]             ` <CAMwawgMDb2ZF9i8T5sxeFqrnf3RRh+thSJXyxPsufFqPC4czBQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-03-07 15:16               ` A A
2023-03-07 15:51               ` Bastien DUMONT
2023-03-07 18:28                 ` A A
     [not found]                   ` <CAMwawgPQN7Jv34tv+kioNYJO-HJ4nhwMco+7BXQCLOEDHDD39A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-03-07 18:42                     ` BPJ
2023-03-07 19:18                     ` bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg
2023-03-07 19:30                       ` A A
     [not found]                         ` <CAMwawgPtfX8+qy4q2nx7+DL-kWhX82QnWh6BQ8CHPyHGZ3uuzw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-03-07 19:37                           ` Bastien DUMONT
2023-03-07 19:48                             ` A A
     [not found]                               ` <CAMwawgPuUvCg1TtGbqz4zsi6-2yJkcAtC27rsx6nNV6id_z6vw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-03-07 20:31                                 ` Bastien DUMONT
2023-03-08 16:16                                   ` A A

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=CAMwawgMDb2ZF9i8T5sxeFqrnf3RRh+thSJXyxPsufFqPC4czBQ@mail.gmail.com \
    --to=amine.aboufirass-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).