Closed torik42 closed 3 months ago
Many thanks, this sounds reasonable and, I hope, fairly straight forward to implement.
For my reference, it'll be this loop that needs updating
Note that it'll need to be documented that paths can not be specified using the y switch.
If anyone else is interested, as a workaround, I currently use
export LATEXINDENT_CONFIG=$(pwd)/indentconfig.yaml
to load a specific subset of additional rules with
# indentconfig.yaml
paths:
- path/to/default.yaml
- path/to/other-config-1.yaml
- path/to/other-config-2.yaml
It’s still not possible to nest them, but one can have multiple lists for different purposes.
This is implemented as of https://github.com/cmhughes/latexindent.pl/commit/1a629f2c9972bff270f459dee5104f188f0b6c61
It'll be part of the next release. Please leave this issue open until I've made the release, hopefully coming soon...
implemented and released at https://github.com/cmhughes/latexindent.pl/releases/tag/V3.24
I would like to have an option to specify local
indentconfig.yaml
files, or even better, include thepaths:
functionality in all the yaml configuration files.Please correct me, if this is already possible. I couldn’t find anything in the documentation and couldn’t make it work. I tried to use
in the local directory and call latexindent with
-l
switch. Theindent.log
showsSo the
/absolute/path/to/config.yaml
was never read.The idea is to have several configuration files with different replacements/configurations (the focus is on replacements, I think) and then choose the correct one according to the project. If the
paths:
entry would be parsed for every configuration file, one could even nest configuration files. This would be useful to allow for fine-grained selection and still providing a preselection in a single file which just loads multiple paths.