Re: Allowing mbsync to respect the XDG base directory specification

[Oswald B. <osw...@gm...>]

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?

>    2. $XDG_CONFIG_HOME/mbsync
>    3. ~/.mbsync (the legacy location)
>
>This patch still respects the --config option superseding these 
>locations.
>
>Please let me know your thoughts, and have a lovely day.
>
see also https://sourceforge.net/p/isync/feature-requests/14/

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

>+.B $XDG_CONFIG_HOME/mbsyncrc
>+If [...] XDG_CONFIG_HOME is set
>+(ususally to ~/.config), mbsync will look for its configuration file named
>+mbsyncrc in that directory
>
that's correct documentation, but bogus behavior - the variable is 
assumed to have a default (it's not even set on my kde system).