public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Ophir Lifshitz <hangfromthefloor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: intermediate LaTeX file
Date: Thu, 6 Aug 2020 04:09:36 -0700 (PDT)	[thread overview]
Message-ID: <f1de51ad-1f67-4374-b216-3b69a8e3e331o@googlegroups.com> (raw)
In-Reply-To: <m2a6zfyyyq.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 1482 bytes --]

See the related issue https://github.com/jgm/pandoc/issues/2288 where I 
suggested using a simple Makefile to produce an intermediate tex file for 
debugging the pdf.

On Friday, July 31, 2020 at 8:47:11 PM UTC-4, John MacFarlane wrote:
>
>
> If you do --verbose, it will be printed to the console (along with a 
> bunch of other stuff, including the exact latex command used). 
>
>
>
> david allen <david...-XkNU/lWsrds@public.gmane.org <javascript:>> writes: 
>
> > When doing md -> pdf is there an intermediate LaTeX file? If so, is 
> there 
> > an option to retain it? 
> > 
> > PS. I enjoyed and appreciate the TUG presentation 
> > 
> > -- 
> > 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-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/pandoc-discuss/07031211-6b72-4c07-b24a-bee8c2238145n%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/f1de51ad-1f67-4374-b216-3b69a8e3e331o%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2891 bytes --]

      parent reply	other threads:[~2020-08-06 11:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-31 13:18 david allen
     [not found] ` <07031211-6b72-4c07-b24a-bee8c2238145n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-07-31 13:47   ` 'oliver...-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org' via pandoc-discuss
2020-08-01  0:46   ` John MacFarlane
     [not found]     ` <m2a6zfyyyq.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-08-06 11:09       ` Ophir Lifshitz [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=f1de51ad-1f67-4374-b216-3b69a8e3e331o@googlegroups.com \
    --to=hangfromthefloor-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).