public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Jason Miller <millerj870-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: pandoc creating folder with name that makes latex fail
Date: Thu, 7 May 2020 07:33:54 -0700 (PDT)	[thread overview]
Message-ID: <e448fa9c-3dfd-4eb8-8e06-01efa9c29384@googlegroups.com> (raw)


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

Pandoc is used to generate a PDF from an R markdown document that has a 
chunk that generates a plot using ggplot2 and a custom function, 
progress.plot.  The chunk looks like this


```{r charts, echo=FALSE, fig.cap="Your progress curve"}

progress.plot(student)

```


The PDF is generated using a LaTeX engine.  I think it uses PDFlatex via 
pandoc.  This is causing a problem that appears to be close to the pandoc 
metal.

It seems like pandoc uses a temporary folder to store the diagram I 
generate with ggplot2.  The name of that folder has as underscore.  This 
means the path to the graphic file, a string that's used in the .tex source 
file, has an underscore.  And the latex compiler doesn't like that.

    ! Missing $ inserted.
    <inserted text> 
                    $
    l.142 ...de2020-05-06_files/figure-latex/charts-1}
                                                       \caption[Your 
progress cu...


The "_files" in the latex log snippet, above, is the name of a folder 
created by pandoc (or Rmarkdown).  I am getting a "Missing $ inserted" 
error before the latex compiler craps out.  No PDF is generated and the 
directory with the figure is deleted.

Is there a pandoc configuration change to take the underscore out of the 
temporary directory's name?  Or is there any other workaround that will 
allow me to generate figures to include in my R markdown document?

Thanks for whatever advice people can share.

-- 
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/e448fa9c-3dfd-4eb8-8e06-01efa9c29384%40googlegroups.com.

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

             reply	other threads:[~2020-05-07 14:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07 14:33 Jason Miller [this message]
     [not found] ` <e448fa9c-3dfd-4eb8-8e06-01efa9c29384-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-05-07 14:43   ` Paul M.
     [not found]     ` <CABoaWcXysCY8fPMXbZj7m3Nc_b763gnjyBGTm-AJNDt87+bARA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-05-07 14:47       ` Jason Miller
     [not found]         ` <38a1639b-1f2f-458d-ab27-2c88968d88bb-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-05-07 16:48           ` John MacFarlane

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=e448fa9c-3dfd-4eb8-8e06-01efa9c29384@googlegroups.com \
    --to=millerj870-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).