No, it is relatively short. The only complexity is the exclude files list. In general most users will only exclude Linux hidden files.
On Fri, Jul 12, 2019 at 1:41 PM Dan Ritter <[email protected]> wrote: > Jerry Feldman wrote: > > I have an application that I wrote where I am using a .ini style file for > > config. I chose that as an afterthought but maybe JSON, YAML, or TOML > might > > be better formats. I set it up that way because I thought my target > > audience might be more familiar with .ini. Right now the code has no > > capability to save the preferences, but that should be an option, so a > more > > Linuxish config file might be better. I'm personally very comfortable > with > > both YAML and JSON. Opinions? (My code is Python3/GTK3). > > It usually doesn't matter. > > If it's short, .ini is perfectly fine. > > If it's a potentially long config file, the best thing you can > do is make it capable of reading a directory worth of files > to include in the main config, so that replacing a small bit > without affecting the rest is easy. > > include /opt/application/config.d/* > > > -dsr- > _______________________________________________ > Discuss mailing list > [email protected] > http://lists.blu.org/mailman/listinfo/discuss > -- Jerry Feldman <[email protected]> Treasurer, Boston Linux and Unix http://www.blu.org _______________________________________________ Discuss mailing list [email protected] http://lists.blu.org/mailman/listinfo/discuss
