I'm not an LSP user myself, but I do want lambdaisland/launchpad to work well for LSP users. With launchpad the classpath will differ from invocation to invocation (depending on which aliases people choose), and can change at any time during runtime when people edit their deps.edn or deps.local.edn.

normally lsp inspects deps.edn or clj-kondo configs and then rescans everything if changes happened. otherwise you can do lsp-workspace-restart manually (in lsp-mode, not sure about eglot, which is the other lsp package in emacs)

does lsp watch for changes to its own config file?

yes

ok, that's great, that does open possibilities. I could alter the classpath command when it changes.

clojure-lsp does re-read its own config periodically, but I don't think there's any way to convince it to re-scan part of the project or its dependencies by changing any of the config, including the :classpath-cmd. AFAIK, that requires a restart of the clojure-lsp server

I think that is the way most clojure-lsp users are used to anyway

That might change when they get used to more dynamic workflows.

If only there was some kind of... protocol. For signaling to the lsp... server, that a rescan is in order.