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: how to enable latex includeonly
Date: Sat, 15 Jul 2023 07:15:36 -0700	[thread overview]
Message-ID: <E9A0A93C-93BC-4494-A22A-7E57BAD810E0@gmail.com> (raw)
In-Reply-To: <ba502360-5898-a5a8-c5b7-c57752eb3a8b-ftuxsla44HXkwd9YShKO9Q@public.gmane.org>

I guess the easiest way would be to add

\let\include\includeonly

or something like that!  Pandoc will interpret the macro.

> On Jul 14, 2023, at 2:03 PM, Jack <jack46-ftuxsla44HXkwd9YShKO9Q@public.gmane.org> wrote:
> 
> Hi
> 
> I'am new in this group and also to pandoc
> 
> I have a latex document with chapters \include'd that compiles well.
> 
> With pandoc I can generate a plain ascii version of it.
> 
> I need to generate a plain version for some included chapters, 
> but when running pandoc it ignores the includeonly and says:
> [INFO] Skipped '\includeonly{P2}' at line 2 column 17
> 
> 
> How can I force pandoc to accept the includeonly?
> 
> 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/ba502360-5898-a5a8-c5b7-c57752eb3a8b%40schuli-wirsi.de.


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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14 21:03 Jack
     [not found] ` <ba502360-5898-a5a8-c5b7-c57752eb3a8b-ftuxsla44HXkwd9YShKO9Q@public.gmane.org>
2023-07-15 14:15   ` 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=E9A0A93C-93BC-4494-A22A-7E57BAD810E0@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).