On Sun, Jun 25, 2023 at 11:55:59AM +0100, Gavin Smith wrote: > > I think "texi2any.init" could be a good name. Another idea is > "texi2any-config.pm" to make it clear it is written in Perl (and, if there > is ever a version of texi2any in the future that is not written in Perl, > would make it clear that the config file is no longer usable).
I think that "texi2any-config.pm" would be much clearer and bear less risk of unintentional use. Another reason for the .pm extension is that .pm files colorization is automatically ok (in vim), not with .init. > A similar use case might be a directory specific init file for gdb > called '.gdbinit'. Other uses like user dotfiles (e.g .emacs, .bashrc) > are not comparable as they are not project specific. I may have misunderstood your point, but this file is actually searched for in such directories, see https://www.gnu.org/software/texinfo/manual/texi2any_api/html_node/Loading-Init-Files.html Another option, more radical, would be to remove completly the possibility to load automatically customization files, and require --init-file to be passed. I do not have any idea whether the 'Config' file feature has ever been used. I have never heard of an actual use, in any case. -- Pat