You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But when I run argdown run pdf test.argdown --cfg argdown.config.js it instead creates foo.pdf in the working directory. I suppose outputPath: "foo/test.pdf" works. But I don't want to hardcode the basename, because eventually I want to use this as an Rmarkdown/Quarto engine that works with programmatically-generated tempfiles.
Edit: It turns out the command line doesn't recognize ad files as argdown files.
The text was updated successfully, but these errors were encountered:
I'm learning my way around the configuration files, and having some trouble setting the output folder.
Here's a minimal argdown file
test.argdown
:What I'd like to do is generate a PDF and place it at
foo/test.pdf
. Here's an attempt at anargdown.config.js
file to do that:But when I run
argdown run pdf test.argdown --cfg argdown.config.js
it instead createsfoo.pdf
in the working directory. I supposeoutputPath: "foo/test.pdf"
works. But I don't want to hardcode the basename, because eventually I want to use this as an Rmarkdown/Quarto engine that works with programmatically-generated tempfiles.Edit: It turns out the command line doesn't recognize
ad
files as argdown files.The text was updated successfully, but these errors were encountered: