mbsync: create groups configuration attribute
This is the end of the configuration that the end-user will use. They will specify an attribute set that contains the name for the group, so they can say `accounts.email.accounts.<aname>.groups.<gname>` to access the configuration for the group with the name `<gname>`.
This commit is contained in:
parent
8bee65350b
commit
00e4a33cd1
|
@ -126,6 +126,20 @@ in {
|
|||
'';
|
||||
};
|
||||
|
||||
groups = mkOption {
|
||||
type = types.attrsOf (types.submodule perAccountGroups);
|
||||
default = { };
|
||||
description = ''
|
||||
Some email providers (Gmail) have a different directory hierarchy for
|
||||
synchronized email messages. Namely, when using mbsync without specifying
|
||||
a set of channels into a group, all synchronized directories end up beneath
|
||||
the <literal>[Gmail]/</literal> directory.
|
||||
</para><para>
|
||||
This option allows you to specify a group, and subsequently channels that
|
||||
will allow you to sync your mail into an arbitrary hierarchy.
|
||||
'';
|
||||
};
|
||||
|
||||
extraConfig.channel = mkOption {
|
||||
type = extraConfigType;
|
||||
default = { };
|
||||
|
|
Loading…
Reference in a new issue