-
Notifications
You must be signed in to change notification settings - Fork 392
feat(lua-api): add Lua API for retrieving Pandoc path #13763
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
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
cderv
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
Is there any use case behind this ?
In LUA there is the Pandoc API already, so I don't see how the pandoc binary can be useful, or even prefered to using the Pandoc's LUA API.
But maybe I am missing something.
I share this concerns because exposing something means we think it could be useful. This is why sometimes we only do some modification when there is feature request or a use case behind. This avoid creating side effect or misusage of feature.
|
Maybe I missed something that is covered by the Pandoc Lua API. |
Cool! Interested to know the use case behind using Pandoc binary inside lua filters. Calling Pandoc binary inside a Pandoc processing worries me, as when we do try to call quarto again with quarto. but maybe I am missing something obvious |
I'm more likely the one that missed something here, because I had the same thought on recursive calls. |
|
Closing as I don't find again the version (not on Git ...) of my experiment where it was useful. |
Expose the path to the Pandoc binary through a new Lua API function
quarto.paths.pandoc().This is a follow up of #13762