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: Obviously not so easy (at least to me)
Date: Sat, 15 Jul 2023 08:54:21 -0700	[thread overview]
Message-ID: <C8325D88-E25B-40E3-8530-835052061AE7@gmail.com> (raw)
In-Reply-To: <d409f430-8f2f-d3c2-7452-34cd2031985d-ftuxsla44HXkwd9YShKO9Q@public.gmane.org>

Sorry, I meant

\let\includeonly\include

Put this before the use of \includeonly in the tex file.  Or you could put it in its own little tex file and put that on the command line before the file you're converting.

> On Jul 15, 2023, at 8:42 AM, Jack <jack46-ftuxsla44HXkwd9YShKO9Q@public.gmane.org> wrote:
> 
> John, can you elaborate on this?
> Compiling this file with latex includes only P2.
> 
> \documentclass{article}
> \includeonly{P2} 
> \begin{document} 
> \include{P1} 
> \include{P2} 
> \include{P3} 
> \end{document}
> 
> 
> Where do I have to add what to get this with pandoc?
> 
> You stanza
>     \let\include\includeonly 
> was not successful, no matter where I put it.
> 
> Regards
> 
> Jack
> 
> 
> -- 
> 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/d409f430-8f2f-d3c2-7452-34cd2031985d%40schuli-wirsi.de.


      parent reply	other threads:[~2023-07-15 15:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-15 15:42 Jack
     [not found] ` <d409f430-8f2f-d3c2-7452-34cd2031985d-ftuxsla44HXkwd9YShKO9Q@public.gmane.org>
2023-07-15 15:54   ` 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=C8325D88-E25B-40E3-8530-835052061AE7@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).