Björn Steinbrink

> Interestingly on Linux the wezterm instance appears to make X server reach 100% CPU [...], but I think that's a separate problem related to my X configuration with Xmonad....

With wezterm started about 3 hours ago and currently 6 windows opened (one at 426x111, the others at 212x111), I see 1.4G RSS, while it was at 1.6GB a few...

Some more data points: The same wezterm instance from before is still running, the memory usage stayed around 1.4-1.5G, but for a few minutes now, whenever I move my mouse,...

I'm using wez's Debian11 Nightly package, which I assume is built with the recommended settings.

Should be good to go

Check errors seem to be from the Github actions being broken, independently from my changes.

Nothing special, just: ``` /target *.rs.bk Cargo.lock .*.swp ``` I originally had .*.swp in my `.config/git/ignore` but added it to the local .gitignore as well, just to make sure that...

As far as I'm concerned, I'd actually be fine with cargo just reporting the directory instead of the individual files. I do wonder whether you would really need additional filtering....

To clarify: It does the right thing because the `target` directory is ignored by the default rule `target/`. If that rule is missing, you get a listing including all the...

Heh, so I found the special case that ignores the target directory [here](https://github.com/rust-lang/cargo/blob/3b142db791ac023a8e8e856c1b18c1ea9367a81a/src/cargo/sources/path.rs#L284) and it's broken in that it doesn't just ignore the target directory, but anything called `target` anywhere...