Describe your proposed improvement and the problem it solves.
Like others before me, I'd like to see there be a default location for a defaults file. My thinking is that a defaults.yaml that lives within $XDG_DATA_HOME/pandoc (i.e. defaultUserDataDir from Data.hs) would be a good location for this, that would hopefully avoid the changing the behavior problem you mentioned in #7007.
You've expressed an openness to this idea in the past, but as far as I could find, nobody has yet taken you up on your suggestion of opening an issue for this, specifically (as distinct from the slightly different behavior that you rejected as changing behavior from #7007, which makes sense to me).
My hope is that having it pull from $XDG_DATA_HOME/pandoc instead will avoid problems with changing behavior in a directory that has a defaults.yaml file in the pwd, while still giving the simplicity of being able to type, for example:
Instead of, say:
pandoc -d ~/.local/share/pandoc/defaults.yaml foo.pdf foo.md
Describe alternatives you've considered.
As a workaround, I'll set up a shell alias as follows:
alias pandoc='pandoc -d ~/.local/share/pandoc/defaults.yaml'
And that will pretty well get me what I need, but it was a surprise to find this behavior (or something very similar) didn't already exist, and I'm hoping that it might in the future.
Thank you for your consideration! (And, perhaps, your or someone's work to implement this. If I knew more Haskel, I might take a stab at a suggested patch. As it is, that'd be a steep ask for me, currently.)
Describe your proposed improvement and the problem it solves.
Like others before me, I'd like to see there be a default location for a defaults file. My thinking is that a
defaults.yamlthat lives within$XDG_DATA_HOME/pandoc(i.e.defaultUserDataDirfromData.hs) would be a good location for this, that would hopefully avoid the changing the behavior problem you mentioned in #7007.You've expressed an openness to this idea in the past, but as far as I could find, nobody has yet taken you up on your suggestion of opening an issue for this, specifically (as distinct from the slightly different behavior that you rejected as changing behavior from #7007, which makes sense to me).
My hope is that having it pull from
$XDG_DATA_HOME/pandocinstead will avoid problems with changing behavior in a directory that has adefaults.yamlfile in thepwd, while still giving the simplicity of being able to type, for example:Instead of, say:
Describe alternatives you've considered.
As a workaround, I'll set up a shell alias as follows:
And that will pretty well get me what I need, but it was a surprise to find this behavior (or something very similar) didn't already exist, and I'm hoping that it might in the future.
Thank you for your consideration! (And, perhaps, your or someone's work to implement this. If I knew more Haskel, I might take a stab at a suggested patch. As it is, that'd be a steep ask for me, currently.)