how to avoid meli/src/conf/overrides.rs being regenerated ?

[teto]

git.meli-email.org seems down at the moment so I am asking here.
I have tried modifying the code to have more debug because meli locks up when using the notmuch backend (maybe because the DB got updated in background) and I dont understand why meli shows "Loading..." in status bar when it looks like everything was already loaded (is there a way from UI to see the meli jobs and what they do ?).
So I've compiled master but I dont know why tools/Cargo.toml got updated and as a result my meli/src/conf/overrides.rs is different and I have a huge diff instead of just seeing my changes.
How can I prevent tools/Cargo.toml from being updated ? is it my fault or the build system (IIRC I just did cargo run)

[epilys]

(I'm in the middle of doing a server migration btw)

I have tried modifying the code to have more debug because meli locks up when using the notmuch backend (maybe because the DB got updated in background) and I dont understand why meli shows "Loading..." in status bar when it looks like everything was already loaded

Looking at the code, the async fetch must have not completed yet (it is done in a Stream fetch, not a single Future, so it can be multiple Futures/jobs)

(is there a way from UI to see the meli jobs and what they do ?).

manage-jobs command (enter COMMAND mode, type manage-jobs and press Enter)

So I've compiled master but I dont know why tools/Cargo.toml got updated

Updated how? It's not part of the global Cargo workspace (root Cargo.toml) at all, so it should be completely independent of everything else 🤔

and as a result my meli/src/conf/overrides.rs is different and I have a huge diff instead of just seeing my changes.

Can you just discard the overrides file with git checkout meli/src/conf/overrides.rs?

How can I prevent tools/Cargo.toml from being updated ? is it my fault or the build system (IIRC I just did cargo run)

It sounds like something else is going on, cargo run should build and run the default executable (the meli binary target in the meli crate)

[teto]

manage-jobs is great. It starts with

8a717e7e-1b40-4afd-900c-3a00fd9c7765  list-mailboxes           2025-01-04 01:41:48  2025-01-04 01:41:48  true                                                                                   
4a0c75d6-4314-4b0e-94ed-b687c161f810  watch                    2025-01-04 01:41:48  null                 -                                                                                      
13823615-44c6-4478-b748-fbefe2130240  fetch-mailbox            2025-01-04 01:41:48  2025-01-04 01:41:49  true 

and follows with screens of 1-second "fetch-mailbox-continued" jobs.
It could be nice to show unfinished jobs (like the watching one, which never finishes I guess) on top.

Meli design reminds me of https://github.com/sxyazi/yazi/, the best software I've discovered these past years. It also has this view of jobs.

Seems like tools/Cargo.lock was a mistake on my part. I've restored the master version. Nevertheless meli/src/conf/overrides.rs always ends up regenerated even after git checkout meli/src/conf/overrides.rs. Can it be due to rust version ? I do something like nix develop nixpkgs#meli which gives me

rustc --version
rustc 1.83.0 (90b35a623 2024-11-26) (built from a source tarball)

Some other mapping I could not find (sry I might have asked this before) but in the compact listing view, how can I force the jump to the previous or next message ? Right now I sometimes have to press 7 or 8 times the "k" or "j" key before being able to select the previous/next message. As I have no visual feedback whatsoever (like a cursor moving on the rightmost message panel), I dont know if it's a bug or feature.

I've just had this issue on my laptop which is 99% due to my setup since the same code worked on my desktop just fine. Tried a cargo clean and rebuilt with same issue:

RROR]: meli::mail::view: Failed to open envelope: OS error 2: No such file or directory: No such file or directory (os error 2)
Sat, 04 Jan 2025 01:53 [ERROR]: meli::mail::view: Failed to open envelope: OS error 2: No such file or directory: No such file or directory (os error 2)
Sat, 04 Jan 2025 01:53 [ERROR]: meli::mail::view: Failed to open envelope: OS error 2: No such file or directory: No such file or directory (os error 2)
Sat, 04 Jan 2025 01:53 [ERROR]: meli::mail::view: Failed to open envelope: OS error 2: No such file or directory: No such file or directory (os error 2)
Sat, 04 Jan 2025 01:53 [ERROR]: meli::mail::view: Failed to open envelope: OS error 2: No such file or directory: No such file or directory (os error 2)

Anyhow will try tomorrow. It's certainly sthg stupid.

seems like the server update succeeded, congrats \o/

NB: I've mapped next_tab but I couldn't find a previous_tab in code.