LSP (rustic) build output goes where?

[grahamas]

I confirm that...

• I searched the FAQ, issue tracker, discussions board, documentation, and wiki, and did not find an answer to my question.

• Any discussions with or conclusions derived from the use of LLMs will be omitted from my question.

What is your question?

In using an LSP (specifically rustic) I'm unsure where the stdout output of the build process is going (upon running SPC m b r which runs cargo run). I can see the output just fine; it's in a weird little sub-window of the code window. But even though I can see it, there are a few problems! I can't figure out any command to move focus to the build output; it doesn't register as a real window so no window switching works (SPC w w skips it) and it's not in any buffer I can find (e.g. via SPC <). Worse, if I switch the code window's buffer and then come back, the weird sub-window is gone, along with all record of what went wrong in my most recent build.

I'm coming back to emacs after 10+ years away, so apologies if I'm overlooking something really obvious.

System information

https://pastebin.com/GFPQTcZW

[wchmb]

Try disabling :ui popup in your init.el.
Otherwise, you can try setting your own custom popup rule with set-popup-rule! for your specific cargo run buffer to not disappear automatically.

[grahamas]

Ahhh gotcha, it was a pop-up. I'm still a bit baffled by the lack of a buffer---I guess that's just a pop-up thing?---but mysteriously the buffer cargo-run is now appearing when the pop-up appears. I can't replicate the lack of buffer now for a bug report, so we'll call this solved, thank you!