Peter Strömberg

> The REPL is probably not much better than what the above commands give A bit unrelated: One thing that springs to mind, looking at how CIDER supports the macro...

> For the hovering, you mean when you hover any macro _use_ you see the expansion there? Yes. That's the only hover we have available. But since it's already a...

If you want to have a feel for how it would be to use a command that would put the expansion in a rich comment, try the command **Calva: Add...

Maybe we're supposed to see more details but it's being presented as `[object Object]`... Can you start clojure-lsp manually? Like just execute `~/.vscode-oss/extensions/betterthantomorrow.calva-2.0.435-universal/clojure-lsp` in the terminal.

Do you see anything useful in the clojure-lsp log? There's a command in Calva for opening it. It's just a file in the temp directory of the system.

Thanks for this suggestion, @djblue! I like the idea to stop and ponder a bit before we continue to just add variables flatly as we have been doing so far....

Another option here is to provide the “variants” of a variable through some syntax. E.g. for `-str` variants, something like `"$(str $file-text)"`. This could potentially open up for other transformations...

Well, we haven't fixed anything around this on purpose, and other changes have been quite unrelated. Did you run it with the Calva test runner, or from the REPL?

> When I reproduce it again, what additional debug info should I collect? What else should I try? There's a command for enabling a printout of a log with messages...

I think we could consider suppressing all these pop-ups and log them in the dev console or in the **Calva says** output channel. Then if someone reports about troubles with...