Fork me on GitHub
#lsp
<
2023-01-23
>
didibus01:01:39

Maybe I'm having a weird issue, but it seems lsp is not able to complete things that you refer? If I don't use the alias, it doesn't seem to complete it? (with the exception of clojure.core)

ericdallo01:01:07

If so, it's on master/nightly builds already, available on the next release (this week)

nice 2
didibus01:01:25

Yup, looks like that, though I'm using refer in the ns form.

ericdallo01:01:18

It should fix that as well, you can try a nightly build at #C032YH7P0R2

didibus01:01:34

Thanks, I'll wait for the release. Glad to know it's already fixed.

didibus21:01:50

Does auto-add-ns-to-new-files? need to have lsp-mode perform file watching? Cause I don't see any ns being added on new files, so that was my first guess?

ericdallo21:01:35

that's enabled by default and no, no client extra setting, probably you have misconfigured source-paths

didibus21:01:51

Ah, ya I think I don't have a deps.edn yet

ericdallo21:01:19

yeah, that explains. You can check the classpath with lsp-clojure-server-info as well

didibus21:01:51

That worked! Though I had to restart the server to pick up the deps.edn changes

ericdallo21:01:56

yes, that's expected

didibus22:01:51

Do I need to restart server every time I change deps.edn ? Just curious

ericdallo23:01:43

ATM yes, we could re-analyze and compute classpath, but would be tricky to not trigger all the time that

didibus00:01:34

Could be a good use case for file-watcher.

didibus00:01:47

Or, I'm guessing LSP doesn't tell the server if a file was saved?

ericdallo01:01:52

There is a notification for that didSave indeed, even so we would need to do a debounce if multiple changes are happening, also compare old classpath and new to know if scan external classpath, lots of variables so probably not worth it

didibus03:01:49

Ya, probably not the next most important feature