No, Calva does not have a visual indicator that an evaluation is currently running.

Hello. Calva relies on clojure-lsp for namespace deriving now. I think you should ask this question in #lsp. We need to update the documentation about this. I'll make an issue for it to be done.

Just so you know, I've now updated the documentation you linked and it now lives here: https://calva.io/namespace-form-auto-creation/

Calva automatically enables lsp, what else should I configure?

I'm not sure, maybe there is some issue with it analyzing your project. @UKFSJSM38 may be able to help you with this. You can check the logs to see if there was an error during analysis. https://clojure-lsp.github.io/clojure-lsp/troubleshooting/#getting-server-log

namespace auto creating only works if your project was analyzed correctly and your :source-paths are correct (or were correctly auto resolved)

You need to check clojure-lsp server log to confirm both, the link @U9A1RLFNV posted ☝️

I’ve shadowcljs.edn and deps.edn both appearing in the project root dir. How does Calva/lsp know what project it is?

ATM it'll consider both

it will get both classpath and merge

For deps.edn, how to specify the :aliaes to merge with?

you need to specify :source-aliases config

check this:

https://clojure-lsp.github.io/clojure-lsp/settings/#source-paths-discovery

Thanks for that info.

By the way, the auto adding namespace part works now. This was due to that I already have a ~/.lsp/config.edn that sets the adding to be false. (which I’ve forgotten).