-
Notifications
You must be signed in to change notification settings - Fork 14
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
Give priority to variables defined in YAML over global settings #103
Comments
Yes, that's a correct assessment.
Yes, from a user POV that makes sense. It's a historically grown problem... When I started John MacFarlane has since added YAML blocks and defaults files to specify settings. They serve the same purpose but I never got round to adding support for them in
It's possible, and I agree it should be handled in some way, but it would be a non-trivial change for which I currently lack the time. 🙁 So my recommendation would be to use one method and stick with it. Either use the functionality Of course, If I ever find the time, I'll add support for YAML blocks and defaults files. For now, I probably need to update the documentation. |
I should add, of course, that if you use YAML metadata or a defaults file, the settings in them don't show up in the hydra menu and you cannot change them there. In that case, there may not be much point in using |
That all makes perfect sense. Thank you for the suggestions. |
Hello |
You can check the |
Hi Joos, I couldn't see that with C-c / V but I could with the log buffer. Sorry I didn't think about this.
It seems the defaults file in the pandoc-mode setting is not passed as an argument to pandoc (expecting -d).
I will open an issue (unless you can also reproducte?)
==================================================
Wed Aug 18 23:50:38 2021
Calling pandoc with:
pandoc --read=markdown --write=latex --output=/home/hugo/filepath/filename.pdf
filename.md: Error in pandoc process
|
If I am not mistaken, variables defined in settings always take priority over conflicting variables defined in a YAML block in the file itself. I assume this is because the settings in practice get sent to pandoc as CLI options, so pandoc gives priority to them.
However, this creates an unexpected behavior. Say I have a global setting that sets a csl or bibliography option for all html output. I would expect that setting to be a default, but if I set a specific value for one of those variables in a YAML block, then that should take priority.
Is there a way to change this? Perhaps implement behavior to ignore global or even file settings if that specific variable has been set in YAML in the file itself, or in an accompanying YAML file?
As always, huge thanks for your generous work.
The text was updated successfully, but these errors were encountered: