birdtray VS cppcoro

> Inability to minimize to tray on Linux

Birdtray [1] works perfectly for this. I think the only thing you have to is create a .desktop file that opens birdtray that opens Thunderbird automatically.

> Inability to easily edit the from address

There is a feature for this for quite a while. In the write message window, just click the down arrow next to 'From' and either choose a pre-configured identity [2] or click "Customize From Address" which allows you to freely edit the from address.

> And TB still doesn't "remember" which -from- addresses are used by which -to- address.

Not sure what you mean, but there is a 'Reply from this identity when delivery headers match' config in account settings. I have never used it, but it allows you to automatically choose an identity when you are replying to a email from a particular address/domain.

[1] https://github.com/gyunaev/birdtray

[2] You can customize as many identities as possible for each server.

You could try birdtray and have a combined calendar and email tray icon. You would kill two birds with one stone if you know what I mean :)

Take a look at Birdtray

There is standalone Qt app https://github.com/gyunaev/birdtray that achieves that by parsing data from Thunderberd's profile.

Thanks for the suggestion, but since the feature landed for Windows for a while now, I would prefer a native solution. Add-ons tend to break after TB major releases and Birdtray has also its problems like Wayland support.

I recently came across Birdtray. It shows unread emails and I can click on it to hide/show Thunderbird. However, if I click again to show the Thunderbird window, I must check the 'Always On Top' box on the Thunderbird window again. If I minimise Thunderbird from it's own minimise window setting - it retains the 'Always On Top' setting - but then takes up space in the panel.

Birdtray* did the trick for me! It's quite useful and the difference from a proper tray integration is almost inoticeable! I have tried kdocker but didn't like it.

releases: https://github.com/gyunaev/birdtray/releases/tag/v1.9.0

PS: Take a look at cppcoro; this might help as well, especially generator<>, if you're looking to generate numbers, and stuff;

This is the only viable implementation.

Kind of sounds like whatever library you were using provided leaky abstractions. Something like cppcoro provides really good abstractions for coroutines, the user really doesn't need to understand why any of it works.

Is there a usecase for copying/serializing such coroutines? If not, I would use the normal C++20 coroutines (cppcoro?).

C++ has the popular CppCoro library. Async_mutex is its equivalent of Tokio::sync::Mutex, providing exclusive access to data shared between tasks.

Because the whole application is running under a single thread there is no need for atomic operations in synchronization primitives(which most of the time requires seq_cst memory order and CMPXCHG which is an expensive instruction in CPU). for example what async_mutex would look like if it knows it's running in a single-threaded scheduler (a non-atomic state variable and waiters queue).

Maybe not old, but I wish cppcoro was still updated. It was such a nice start!

You can get generator<> from https://github.com/lewissbaker/cppcoro

It is possible to compose them more easily than described in the article; Lewis Baker's cppcoro library for example provides a recursive_generator<> type[0] that allows this without using any macros. It's up to the library part of coroutines to make things easy, end users are not expected to write low-level coroutine code themselves.

I wonder about the allocation elision. Return value optimization became mandatory, and some compilers can already elide calls to new/delete and malloc()/free() in normal code, so perhaps it will be possible to guarantee allocation elision in the future in the most used cases.

[0]: https://github.com/lewissbaker/cppcoro#recursive_generatort