David Barsky

Sorry, I thought I replied, @otiv-emiel-vanseveren. > It looks like I'll need to [update the existing rust-project-gen](https://github.com/bazelbuild/rules_rust/blob/802274cc6a73a7027852b9b7d719b4413a8acec9/tools/rust_analyzer/main.rs) similar to the one Buck has (reference above)? Yup! > mainly what buck's...

@sam-mccall As a preface, I don't really understand or *know* Blaze/Bazel, so I might say things that don't really make sense or aren't applicable. > I have a hacked up...

@sam-mccall > Yeah, I think technically `root/` in the filesystem is `@//` in blaze-label terms (main repository, root). But I think multi-repo is not so relevant here, so I'd usually...

If `cargo check` is fast, then the `flycheck` module in rust-analyzer is doing fine: the issue is within rust-analyzer's macro expansion infrastructure (I have a minimal reproduction for `macro_rules!`-based macros...

Sorry for the delay. What do you mean by “status line”? Which command are you referring to?

@arxanas Ah! Yes, I believe it does, if I'm understanding you correctly (see below). At the risk of emphasizing something already obvious to you, I'd "just" like `jj resolve` to...

It would, yes! I'd also be happy to send a PR that copies [this snippet](https://github.com/jj-vcs/jj/blob/43ac4faac4780e45c55708dbaf55d5d95614e858/cli/src/commands/status.rs#L127-L135) from `jj status` over to `jj resolve`, if you'd like! (Naively, it seems like a...

Small update: #5111 helps, but I still find myself running `jj st` often to check for the blue "Hint: Conflict in parent commit has been resolved in working copy". Since...