printfn

The flag is important because it prevents fend from auto-simplifying any calculations that are explicitly converted to a specific unit with `to`. For example: ``` > 4 watts * 3...

Thanks for the PR, and sorry for the delay in reviewing this. I'll try and take a look at this and your other pull request in the next couple days.

Thanks!

Would it be possible to get a new release with this feature included?

> > Correct - just add the mount option to your fstab > > […](#) > > what mount option would that be? Sorry am a bit dumb :p The...

`cargo-bisect-rustc` identified this commit: https://github.com/rust-lang/rust/commit/a70b2ae57713ed0e7411c059d582ab382fc4166a. searched nightlies: from nightly-2024-06-07 to nightly-2024-07-20 regressed nightly: nightly-2024-06-10 searched commit range: https://github.com/rust-lang/rust/compare/f21554f7f0ff447b803961c51acafde04553c1ed...a70b2ae57713ed0e7411c059d582ab382fc4166a regressed commit: https://github.com/rust-lang/rust/commit/a70b2ae57713ed0e7411c059d582ab382fc4166a bisected with cargo-bisect-rustc v0.6.9 Host triple: x86_64-unknown-linux-gnu Reproduce with:...

I've tracked down the regression to the `unicode_width` crate, which was updated from 0.1.12 to 0.1.13 in this PR: https://github.com/rust-lang/rust/pull/126172. The PR https://github.com/unicode-rs/unicode-width/pull/45 updated widths of control characters from 0...

I don't think either `0` or `1` width is correct, rustfmt needs to properly calculate the tab width to make it consistent. Here's an example that's broken with Rust 1.81's...

That's not correct, only the behaviour for newlines was reverted; the behaviour for tabs and other control characters has not been reverted. Regardless, passing any ASCII character

This is normal Cargo behaviour and not something that Atuin could change. You have to run `cargo install [email protected] --locked` for Cargo to respect the lock file and not automatically...