dpc
@harsh-ps-2003 Go for it, PRs always welcome.
Whoever shows up with a PR first wins. :D > Can I get bit more context of what we are working on to get a better understanding to solve the...
stdout will flush on newlines (uses [std::io::LineWriter](https://doc.rust-lang.org/std/io/struct.LineWriter.html#) under the hood). Should be natural for any logging library to just write-out stuff in lines (or use `LineWriter` to gather output into...
This will be a bit off-topic for PR, but relevant to the topic of "false negatives". [`typos`](https://github.com/crate-ci/typos/tree/master) takes a different approach where it matches again common mispellings instead of against...
@pascalkuthe Yeah, I was not suggesting that approach in Helix. I think typos shines in CIs to enforce some base level of quality, where false positives are very very annoying....
As a workaround I can just use `rev=$(git rev-parse ${tag}^{commit})` to always point at the commit it in all invocations.
AFAICT, still happens with `nix_2_23`
Replace existing usages with explicit `Watch` channels, get rid of the whole thing (notification mechanism)?
IMO we should just get rid of the whole thing. How many explicit channels would we need anyway?
Oh, this will be implemented? Cool. BTW. I think if you use `Fix #xyz` in the PR/commit msg it will close the issue as "Solved" instead of "Closed".