cargo-edit is a really nice way of managing Cargo.toml without a text editor: https://github.com/killercup/cargo-edit/ (feels like the comfort of npm)
miniblog.
Related Posts
I carefully document `cargo install --locked` for difftastic users, I carefully use `--locked` for CI, and I've just realised that all my release builds totally ignore it! Oops.
Anyone using my prebuilt binaries have been getting different Unicode width calculations in display.
I'm surprised there aren't more tools out there for starting a new project with some default config files.
There's `cargo new` but it's Rust specific and very minimal. create-react-app is React specific.
The only option I know of is cookiecutter. Surely it's a common problem?
One subtle behaviour of Claude that wasn't obvious to me: whilst each conversation is transient, permissions persist across conversations.
So if you've given permission to run e.g. 'cargo test' or even 'cargo run', you need to be sure that all future invocations are safe too.
You can see the current permissions with /permissions.