On 20/05/08 10:56AM, Oswald Buddenhagen wrote: > On Thu, May 07, 2020 at 05:46:42PM -0500, Wyatt Sheffield wrote: > > Considering this, I would like to submit the following patch which has > > mbsync look for a config file in 3 places in the following order: > > > 1. $MBSYNC_CONFIG - a user-set environment variable > > > is there any actual point in that?
I use several programs that support environment variables for their config file locations among other things. It just adds flexibility for the user to configure their system as they see fit. While not strictly necessary, I find it nice to have the option. And at only 3 extra lines of source code I decided "why not?" > > +++ b/src/mbsync.1 > > +By default, the configuration is read from $MBSYNC_CONFIG first, then > > +$XDG_CONFIG_HOME/mbsyncrc, and finally ~/.mbsyncrc. > > > this formulation suggests that all three are actually read. You're right - I should be more clear. If the first location can't be read, it tries again at each subsequent location until a config file is found. _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
