You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the way that Thunderbird profiles work, to add an account accountname to a profile profilename, you add the profile profilename to the list of the option accounts.email.accounts.accountname.thunderbird.profiles.
The way I think about profiles (and I would argue this is not uncommon), is that a profile "decides" the collection of the accounts that belong to that profile.
That way, I can reuse profiles between different setups, and I don't need to worry about the profiles in the accounts.email.accounts setting and change it according to which profiles I have decided to include for a specific setup. To me, accounts are just accounts, they don't themself decide which thunderbird profile they belong to, this should be "up to the thunderbird profile to decide", so to speak. Intuitively, to me, Thunderbird profiles are exactly that: a collection of accounts. The other profile settings seem almost minor to me. If I want to reuse my mailaccount somewhere, I don't want to worry about if the profiles specified there actually exist, or have to change them according to that other place I use them.
I get why the other way around (that is currently used) makes sense: Profiles can be understood as "account-agnostic", and accounts are where it is decided what they belong to.
I currently have a DIY module that does what I want, but I wonder if it is worth it for me to make some PR that adds an option such as programs.thunderbird.profiles.<name>.accounts (that in some way possibly has to be mutually exclusive with accounts.email.accounts.<name>.thunderbird.profiles).
Of course, in the setup of most people, this distinction hardly matters, as most people have all profiles and all emailaddresses everywhere.
The text was updated successfully, but these errors were encountered:
Currently, the way that Thunderbird profiles work, to add an account
accountname
to a profileprofilename
, you add the profileprofilename
to the list of the optionaccounts.email.accounts.accountname.thunderbird.profiles
.The way I think about profiles (and I would argue this is not uncommon), is that a profile "decides" the collection of the accounts that belong to that profile.
That way, I can reuse profiles between different setups, and I don't need to worry about the profiles in the
accounts.email.accounts
setting and change it according to which profiles I have decided to include for a specific setup. To me, accounts are just accounts, they don't themself decide which thunderbird profile they belong to, this should be "up to the thunderbird profile to decide", so to speak. Intuitively, to me, Thunderbird profiles are exactly that: a collection of accounts. The other profile settings seem almost minor to me. If I want to reuse my mailaccount somewhere, I don't want to worry about if the profiles specified there actually exist, or have to change them according to that other place I use them.I get why the other way around (that is currently used) makes sense: Profiles can be understood as "account-agnostic", and accounts are where it is decided what they belong to.
I currently have a DIY module that does what I want, but I wonder if it is worth it for me to make some PR that adds an option such as
programs.thunderbird.profiles.<name>.accounts
(that in some way possibly has to be mutually exclusive withaccounts.email.accounts.<name>.thunderbird.profiles
).Of course, in the setup of most people, this distinction hardly matters, as most people have all profiles and all emailaddresses everywhere.
The text was updated successfully, but these errors were encountered: