Václav Kubernát

I have tested that https://github.com/ultrabug/py3status/commit/f6da6b8acc141011717a7c24c1f90b12352dce8a does introduce this bug. The commit before that works fine (it also had something to do with HTML formatting)

Yes, that helps. Thanks! I wasn't aware of the `markup` setting.

I'm not sure if `markup = "pango"` is just a workaround or if my problem is an actual bug. Feel free to close this issue if it's not a bug.

I see. Well, it won't be possible for me to rework everything to std::expected (although I like the approach). I was wondering: would it be possible to assign a custom...

Ideally, I would still like to preserve throwing from `co_await coro;`, and only abort, when the coroutine is NOT awaited. I'm not sure if that's even possible. > So I'm...

This is the discussion thread for JS: https://github.com/nodejs/node/issues/20392 It seems that it's a matter of opinion rather than some kind of a technical issue. It seems that the creators of...

Thanks for the update. I'm going to try the new feature. 1) Yeah, I'm fine with another class instead of a template argument. However, `UnawaitableTask` implies that you can't use...

I have tried the new branch, but it seems that I'm doing something wrong. Exceptions are still being caught. Or rather, I would think that this program would crash, but...

>Regarding the Generator & exceptions - the exception from the generator should be re-thrown when you dereference the iterator, which, combined with the TaskWhereUnhandledExceptionsAbort should cause the code to terminate....

Also, it seems that it does not exactly where the iterator is, if one exception was thrown, you can advance the iterator as much as you want and the next...