himalaya VS cargo2nix

Before you going deeper, take a look at himalaya if it fit to your needs.

https://github.com/soywod/himalaya this one also is a thing, has a vim plugin too

Take a look at Himalaya: https://github.com/soywod/himalaya

You can use himalaya for that

We live in a time of a Renaissance of terminal tools. I recently discovered Himalaya[1], a command line tool for email, and I really like it. I'm also interested in exploring a new tool for calendar called qcal[2]. I'm kicking around writing a chat client for GroupMe for the terminal right now. That way I could finally ditch pidgin.

Like the OP, I spend all day in tmux these days, which is in many ways the most superior UI[3]. As a bonus, CLI tools are often cross-platform and very easy to write.

1: https://github.com/soywod/himalaya

- Rust projects are built with https://github.com/cargo2nix/cargo2nix. We chose cargo2nix to get incremental builds, meaning that dependency builds can be shared between our Rust projects and that not all dependencies have to be rebuilt when adding/updating/removing dependencies from a project.

We used cargo2nix to generate top-level Cargo.nix file that we committed to the repository (we didn't allow generating nix files on CI for security and reproducibility reasons).

There's a cross compile example that works for at least 3-4 targets on Linux and uses proc macros. Pretty sure the situation you described is no more complex.

Release notes. Last announced release was 0.9.0.

Nix already solves this problem and can handle dependencies and building projects across a range of languages (including Rust via Cargo2nix) and reproducible machine configuration.

Building with nix, for instance with cargo2nix (https://github.com/cargo2nix/cargo2nix), could be safer if sandboxing is enabled.

cargo2nix