Michał Siedlaczek

> The Emails are sorted in the user's preferred order. Hmm, that complicates things, checking each time for which messages are new could be terribly inefficient. I suppose this could...

> The biggest change is that you've moved the code to libmutt (I guess to make the testing build) > libmutt is the library functions that have no dependencies, so...

> All the structures are in-memory, so it probably won't be that slow. > (and this will be a temporary step in development, so I don't think we need worry)...

@flatcap I created a new optional lib, but I think I'm doing something wrong. I don't seem to compile my tests when i define the flag, though `./configure` output looks...

Ah, thanks for giving it a look!

@flatcap I was just looking into storing last time of notification... these must be per mailbox, right? to work correctly... The question is: how to store these? Should I create...

Thanks for the explanation. I pushed some changes, and I started testing it after changes to see if it works as expected. I guess there's still a question of expandos...

I must be missing some important point here... I kept getting a segfault on access to an email, so I debugged it, and I see some of those emails in...

I am at a loss here. Here's my test: (1) starting with empty gmail Inbox, (2) sending an email, (3) running neomutt with some debug messages printing: `msg_count`, `msg_unread`, and...

@flatcap I made some changes, and I think this is currently working as I expect it to. I'm running it for my own workflow to find any potential issues. A...