New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pandoc not finding custom writer #2625
Comments
Does the data file directory pandoc: Could not find data file /usr/local/Cellar/pandoc/1.16/share/x86_64-osx-ghc-7.10.3/pandoc-1.16/data/templates/default./users/noamross/library/r/3.2/library/ehastyle/outbreak.lua actually contain ..templates/default./ ... with the period after default? |
There is no default template for custom lua writers. So you need to specify the template using --template What's happening is this. When you do 'pandoc -t latex -s', This isn't such good behavior; I will change it so that +++ Noam Ross [Jan 06 16 14:19 ]:
|
Previously, if you tried to do `pandoc -s -t /path/to/lua/script.lua`, pandoc would look for the template in `~/.pandoc/templates/default./path/to/lua/script.lua`. With this change it will look in the more reasonable `~/.pandoc/templates/default.script.lua`. This makes it possible to store default templates for custom writers. Closes jgm#2625.
Previously, if you tried to do `pandoc -s -t /path/to/lua/script.lua`, pandoc would look for the template in `~/.pandoc/templates/default./path/to/lua/script.lua`. With this change it will look in the more reasonable `~/.pandoc/templates/default.script.lua`. This makes it possible to store default templates for custom writers. Closes jgm#2625.
Running pandoc (via rmarkdown in R) with a custom writer like so:
I get the following error:
I can confirm that
/Users/noamross/Library/R/3.2/library/ehastyle/outbreak.lua
exists. The long path to the pandoc directory is due to the installation being via homebrew, but it's the right path. Pandoc seems to not find the writer file and try to find it in the default directory instead.I get the error when running pandoc directly in the command line, as well. Sometimes I _don't_ get this error when I remove some of the other arguments, though I haven't been able to figure out exactly which combination does this.
The text was updated successfully, but these errors were encountered: