Clément DOUIN

> I installed himalaya like this, do I need more features by any chance? Nop, it should definitely work like this. > Oh, and in March 2024 I ran an...

I suspect Himalaya CLI not to take the latest version of `secret-lib` and `keyring-lib`. I pushed a fix, could you try to install it again and see? ```sh cargo install...

I propose you a last thing, instead of using `cargo install` could you use git directly? ```sh cargo uninstall himalaya git clone https://github.com/pimalaya/himalaya.git cd himalaya cargo run --features keyring --...

> However this time I didn't get a popup once about Keychain access with my self-compiled himalaya binary. Don't really know why, but that might be the reason it can't...

I created a new branch `keyring-debug` where I pushed an example and a binary. Could you please try the following: ```sh cd /path/to/himalaya git fetch git checkout keyring-debug # first...

> So I don't think when you read the secret in the end you are actually reading it from the Keychain. It should definitely be the case. In fact, it...

I think I finally understood what happened. The low-level `keyring-rs` crate uses mock keystore when no keystore matches the current OS. And it does not support logs, which means you...

Which version of Himalaya do you use?

I would advise to either use `master` branch or wait for the `v1`. New versions support collections of Maildir (alla mbsync), while previous version were only supporting Maildir++ variant.

> Try to check `master` version, but I have error when build using flake: I'm in the process of cleaning core libs and releasing `v1`, it should be fixed as...