Clément DOUIN

This has been fixed recently but not yet applied for Himalaya CLI: https://github.com/pimalaya/tui/blob/6e51e2565afec4b44bdaaaacc0eacbe63bba4fe0/src/himalaya/wizard.rs#L43 The fix should land very soon. I will close the issue when it's ready!

The fix landed on `pimalaya-tui-refactor`, which should be merged into `master` very soon.

I am not sure, but I think it has been fixed on `master` recently. Which version do you use, and how did you installed it?

Curious to know if `f9f2aae` will work, last builds are supposed to be statically linked and should work like before. But I did not have the opportunity to try on...

Happy to hear that the last statically-linked builds work as expected on Windows. I finally took time to properly read your initial issue, which in fact is not really one....

I see what you mean. It's part of a bigger problem, where every action is tieded up to a folder or mailbox. IMAP works this way be design. This makes...

Regarding the JSON output of the `attachment download` command, I would advise to subscribe to #547. I will extend its scope. Regarding the download directory, I agree to make it...

Here the error I get: ``` error[E0277]: `std::sync::mpsc::Sender` cannot be shared between threads safely --> src/backend/imap/backend.rs:404:10 | 404 | impl { | ^^^^^^^ `std::sync::mpsc::Sender` cannot be shared between threads safely...

> That would also enable the multi-threaded access patterns that I think > @soywod wants to work with. I am really interested in this solution, because the actual implementation I...

I initiated a PR, please let me know if it resembles what you had in mind.