Hi,

I've recently moved one of my account from using IMAP to using Maildir 
and I've noticed a bug I didn't have before.

Unread messages in subfolders are not being displayed in the dirlist at 
start. They get displayed only if I moved to that folder or if I run the 
check-mail command (then they get displayed in all subfolders).

Using aerc 0.15.1 (also tested on master branch).
My config doesn't run check-mail at start (default value of 0).
The check-mail command is a run of mbsync.

The sync is already being run regularly in the background independently 
of aerc. It seems to me that aerc should then be able to display those 
unread messages directly at start without requiring running the sync 
again for nothing and waiting for its completion.

--
Damien

Hi,

I'm going to bump again this topic I didn't get any reply to, with 
hopefully a better explanation of what I see as an annoying limitation 
of the maildir support.

My desired workflow is the following. Using a maildir account, I'm 
running independently of aerc some regular background syncs. Whenever my 
system detects a new mail from the latest sync, I want to open aerc and 
immediately have the new mails being displayed in the dirlist whatever 
the subfolder they are in.

Right now, as I explained in my previous post, this isn't the case and 
I'm left wondering where are the new mails. I need to either go to every 
subfolder to trigger the display of the new mail in it, or run another 
sync within aerc via the check-mail command. Both of these options are 
clearly not great with a large number of subfolders, or a sync that 
takes a long time to finish.

I've managed to find a workaround using the following config:
check-mail = 1m
check-mail-cmd = exit 0
However this is clearly a hack and it also now prevents me from running 
a sync within aerc whenever I don't want to wait for the next background 
one.

I believe my workflow is not unreasonable and I also expect that 
checking the local maildir for new mails at start shouldn't be expensive 
to do. Thus I would appreciate if this could be considered.

Thank you

--
Damien

On Sat May 13, 2023 at 8:15 PM CEST, Damien Tardy-Panis wrote:
> Hi,
>
> I've recently moved one of my account from using IMAP to using Maildir 
> and I've noticed a bug I didn't have before.
>
> Unread messages in subfolders are not being displayed in the dirlist at 
> start. They get displayed only if I moved to that folder or if I run the 
> check-mail command (then they get displayed in all subfolders).
>
> Using aerc 0.15.1 (also tested on master branch).
> My config doesn't run check-mail at start (default value of 0).
> The check-mail command is a run of mbsync.
>
> The sync is already being run regularly in the background independently 
> of aerc. It seems to me that aerc should then be able to display those 
> unread messages directly at start without requiring running the sync 
> again for nothing and waiting for its completion.
>
> --
> Damien

On Thu Jul 27, 2023 at 3:38 AM CDT, Damien Tardy-Panis wrote:
> Hi,
>
> I'm going to bump again this topic I didn't get any reply to, with 
> hopefully a better explanation of what I see as an annoying limitation 
> of the maildir support.
>
> My desired workflow is the following. Using a maildir account, I'm 
> running independently of aerc some regular background syncs. Whenever my 
> system detects a new mail from the latest sync, I want to open aerc and 
> immediately have the new mails being displayed in the dirlist whatever 
> the subfolder they are in.

Hi Damien -

When you say "open aerc", do you mean a currently running instance or a whole
new instance? I don't use maildir but looking at the way the worker is set up,
it should be listing all folders and their unread counts at startup. Do you see
any errors in your logs that might be preventing this from happening?

-- 
Tim

Hi Tim,

Thanks for replying.

> When you say "open aerc", do you mean a currently running instance or 
> a whole new instance?

I meant opening a whole new instance.

> I don't use maildir but looking at the way the worker is set up,
> it should be listing all folders and their unread counts at startup. Do you see
> any errors in your logs that might be preventing this from happening?

I've tested again with logging enabled but I don't see any error there.

Here is an interesting thing I forgot to mention earlier though: the 
unread mails that have been seen before by aerc (meaning in maildir 
terms: the ones within the "cur" directories) are displayed properly at 
start, even in subfolders. The issue concerns only the completely new 
ones (which are in the "new" maildir directories).

I'm also seeing another unrelated bug I think with my workaround: the 
new mails are displayed in the dirlist but they are not styled properly 
as "unread".

--
Damien