Skip to content
Prev 371256 / 398530 Next

post_processor in rmarkdown not working

On 07/09/2017 10:11 AM, Thierry Onkelinx wrote:
Not working for me either right now for some reason or other.  What I 
was doing was manually running debug(post_processor) in the debugger 
after single stepping past its definition.

What does show it is running is that at that same point I can execute

post_processor <- function() stop()

and it stops.

The end of the console log looks like this:


/Applications/RStudio.app/Contents/MacOS/pandoc/pandoc +RTS -K512m -RTS 
skeleton.utf8.md --to latex --from 
markdown+autolink_bare_uris+ascii_identifiers+tex_math_single_backslash 
--output skeleton.tex --template 
/Library/Frameworks/R.framework/Versions/3.3/Resources/library/INBOmd/rmarkdown/templates/rsos_article/resources/template.tex 
--natbib --bibliography sample.bib
Latexmk: This is Latexmk, John Collins, 19 Jan. 2017, version: 4.52c.
Error in output_format$post_processor(yaml_front_matter, utf8_input, 
output_file,  :
   unused arguments (yaml_front_matter, utf8_input, output_file, clean, 
!quiet)
Called from: output_format$post_processor(yaml_front_matter, utf8_input, 
output_file,
     clean, !quiet)

so we see pandoc being run, then Latexmk, then the post_processor call. 
It seems a little odd that Latexmk is being run.  Is that something you 
are doing, or is it pandoc asking for that?  If the latter, can you tell 
pandoc not to do so?
I'm not sure you would normally have write access in that directory, so 
it may not be typical of what you'd see in a user directory.  I 
certainly see something different when I copy the skeleton.Rmd file (and 
nothing else) to my own temp directory.
That certainly indicates it isn't doing what you want, but it might be 
running and doing something else.

Duncan Murdoch