What are your thoughts on having the style (theming) as a separate
config file (ie theme.conf or similar)? This would make it easier to
share premade themes, possibly even distributing some common ones with
Alternatively, maybe adding a "theme" configuration option to aerc.conf
that would specify the name of the theme to use, and pull from files in
aerc's share folder or the user's config location.
Multiple themes could also be applied sequentially to overwrite prior
style directives, as Reto mentioned.
Would that still allow, for example, unread + flagged messages to be a
specific colour? Or recipient to be a different colour?
Wondering if it's feasible to have hierarchical settings, like:
Or is the plan to include support for regex overrides?
This is WIP of the style/color configuration for Aerc as I suggested
I have setup very basic configuration for msglist just to test the
You can customize the styles used in tcell contexts by providing
`[styles]` section in aerc.conf which provides the default style.
Styles for individual objects can be customized as children to the
styles sections as seen in the example below.
The issue I'm having with that approach is that it would be great if one could
do a similar thing as with the rest of the UI config. Namely do that conditionally.
Say you want to color every patch green for whatever reason, flagged messages red.
Oh and naturally the base colors change per account (work vs private etc).
Do you know what I mean?
Now, if we have the above but do that conditionally you end up with a gazillion
I'd rather have a single [style] section that can be overridden by other, more
specific sections like [style:subject~regex] and the likes.
I like the idea of regex to customise colours. To mention Mutt again, I
use that to highlight emails from certain recipients or containing
specific subjects, which is really helpful.
Any colour configuration would be welcome though... this the main
feature I've been waiting for before attempting to migrate off Mutt.
I am not too sure, I am too happy to have index_fg, index_bg, etc.. as
there would be more attributes like bold and underline. which would mean
we have 4 fields per item.
Another suggestion would be to have a single line style per item like so
index_unread=bg:yellow bold underline
This would be a bit more consise allow setting defaults during