Re: file/directory named Config in current dir causes waring from texi2any

[Gavin Smith]

On Sun, Jun 25, 2023 at 04:18:51PM +0200, Patrice Dumas wrote:
> 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.

To update this discussion, that was the name I changed it to.  Is it worth
a mention in NEWS?

> > 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
> 

You're right, it could be project-specific or not.