When multiple stylesets are configured in aerc.conf they are passed as a
comma-separated list of full paths to colorize. The patch splits that
list into separate paths and processes them one by one, effectively
applying the stylesets one after another as in aerc itself.

Signed-off-by: Vitaly Ovchinnikov <v@ovch.ru>
---

v1: initial version
v2: fix potential memory leak
v3: fix problem if

 filters/colorize.c | 89 +++++++++++++++++++++++++++++-----------------
 1 file changed, 57 insertions(+), 32 deletions(-)
[message trimmed]

When multiple stylesets are configured in aerc.conf they are passed as a
comma-separated list of full paths to colorize. The patch splits that
list into separate paths and processes them one by one, effectively
applying the stylesets one after another as in aerc itself.

Signed-off-by: Vitaly Ovchinnikov <v@ovch.ru>
---

v1: initial version
v2: fix potential memory leak

 filters/colorize.c | 87 +++++++++++++++++++++++++++++-----------------
 1 file changed, 56 insertions(+), 31 deletions(-)
[message trimmed]

When multiple stylesets are configured in aerc.conf they are passed as a
comma-separated list of full paths to colorize. The patch splits that
list into separate paths and processes them one by one, effectively
applying the stylesets one after another as in aerc itself.

Signed-off-by: Vitaly Ovchinnikov <v@ovch.ru>
---
 filters/colorize.c | 86 +++++++++++++++++++++++++++++-----------------
 1 file changed, 55 insertions(+), 31 deletions(-)

diff --git a/filters/colorize.c b/filters/colorize.c
index 9de91480..6d2559a1 100644
--- a/filters/colorize.c
+++ b/filters/colorize.c
[message trimmed]

> Thanks for reporting this. It is definitely related to go-opt. I will
> fix it.

Great!

> 	:prev-folder -- -100

That's fine, not a big deal to add this.

-- Vitaly

> Applied, thanks.

Not sure if it is related to go-opt update, but aerc crashes there every
time I try using `:filter`. Here's what I get after `:filter` without
parameters. Same with parameters, though.

Version: 0.20.1-55-gde15b7c794e3 (go1.23.4 arm64 darwin 2025-03-31)

This error was also written to: /tmp/aerc-crash-20250331-103015.log
panic: *account.SearchFilter.EndDate: unsupported field type: struct [recovered]
        panic: *account.SearchFilter.EndDate: unsupported field type: struct

goroutine 1 [running]:
git.sr.ht/~rjarry/aerc/lib/log.PanicHandler()

> Not sure I understand. The `-u` option I was mentioning would behave like so:
> `:next-folder -u` would navigate to the next non-empty folder (likewise for
> `:prev-folder -u`). So skipping empty folders as you said. Did you think of
> anything else?

My suggestion was not about skipping empty folders, it was rather about
letting me jump between folders with messages, doesn't matter seen or
unseen.

-- Vitaly

> Yes totally, it didn't cross my mind. I'll add the `-u` option instead for
> version 2.

What about another option for non-empty folders, so we can skip the
empty ones in a similar manner?

-- Vitaly

The patch allows to highlight messages in specific accounts without
affecting the others.

Without the patch you need to copy the whole styleset, add the
highlighting commands, then use that styleset with that specific
account.

With the patch you can make a small styleset with just the highlighting
stuff and chain it up to the main styleset this way:

        styleset-name: main
        [ui:account=special]
        styleset-name: main,highlight
[message trimmed]

Changelog-added: Stylesets can be chained-up in `styleset-name` config
    parameter using comma-separated format.
Signed-off-by: Vitaly Ovchinnikov <v@ovch.ru>
---

The idea behind the patch is to allow highlighting of messages in
specific accounts without affecting the others.

Without the patch you need to copy the whole styleset, add the
highlighting commands, then use that styleset with that specific
account.

With the patch you can make a small styleset with just the highlighting
stuff and chain it up to the main styleset this way:
[message trimmed]

> I can repro, alacritty + tmux. That first emoji (🤦‍♂️)) seems to be really
> breaking tmux + alacritty and I am not sure why yet.

I got another email with a different set of emojis that breaks drawing
the similar way. The raw subject header is:

Subject: =?UTF-8?B?UlFIViA4REwgRTM5IPCfkanwn4+74oCN4p2k77iP4oCN8J+Si+KAjfCfkanwn4+9IENvbQ==?=
        =?UTF-8?B?cGxldGVkPyBTdGF0dXMgb2YgUGxhbiBFeHRlbnNpb24gSW5hZGVxdQ==?=

Hope this helps.

-- Vitaly