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
On 20/05/08 05:34AM, Aaron W. Swenson wrote:
> On 2020-05-08 10:56, Oswald Buddenhagen wrote:
> > On Thu, May 07, 2020 at 05:46:42PM -0500, Wyatt Sheffield wrote:
> > >+.B $XDG_CONFIG_HOME/mbsyncrc
> > >+If [...] XDG_CONFIG_HOME is set
> > >+(ususally to ~/.config), mbsync will look for its configu
On 2020-05-08 10:56, Oswald Buddenhagen wrote:
> On Thu, May 07, 2020 at 05:46:42PM -0500, Wyatt Sheffield wrote:
> >+.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
> >
>
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?
Hello, all!
I have found mbsync to work well for me, but encountered minor frustration in
regards to the default
config file location. I like to keep my $HOME very clean (in stark contrast to
my home), and
therefore tend to keep all my configuration files in ~/.config. This was not a
huge issue
