When you run lein classpath yourself does it return any errors? I’ve encountered an error message like this myself, and it’s usually been my fault.

Actually, yes, it does return an error, but here's the pinch, it's not a catastrophic error, since I'm using clojure deps to fire up the repl, not lein

Thus, I'm not concerned that lein is returning an error, in fact, I would say this is slowing down lsp from starting up, for it maps through all the default project specs to gather up the classpath

I think I will have to tell lsp that I only want it to run deps -Spath

Yeah, I added

:project-specs [{:project-path "deps.edn"
                  :classpath-cmd ["clojure" "-A:dev:test" "-Spath"]}]

to my $HOME/.lsp/config.edn and all is fine

Be aware that this will make clojure-lsp always ignore lein for every project you run since you added to your home

Also, eve clojure-lsp saying classpath lookup failed for lein, it will safely use the deps.edn one, so you can just ignore if for some reason the lein error makes sense

indeed

it was just a new error that didn't happen before

without a comforting message that it worked with gather the classpath from deps

We have this message error for some time now, and since the error happens with only running lein classpath, it'srelated with your project indeed and not clojure-lsp

you just need to understand why it didn't happen before

Strange. I know why it's happening (can't resolve a JAR)

it can't resolve the JAR if our VPN is down

and that's not the first time it's been down..

we have this all the time at nubank 😅 lein classpath fail if we don't have aws creds setup since we have our maven repository at s3

so it's pretty common to see folks complaining there that clojure-lsp is not working because their forgot to setup aws creds and lein classpath fails

that's why I added the command clojure-lsp runs on the message

yeah, we have s3 too 🙂

I guess it's fine now, I know how to handle the issue if it arises (yup, we're migrating to deps from lein...but having a transition period)

probably related with wrong source-paths configuration

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

not sure, once the symbol is complete lsp shows the signature doc for instance

ex with clojure.string/includes?

no completion on it but it does show the signature when in (clojure.string/includes?|)

I have to run, bbl

The signature has nothing related with the completion, I suspect your source-paths are wrong indeed

doubt it, my deps.edn has only src

:paths ["src"]

lsp-server advertises :source-paths ["src" "test"],

anyway, I ll check this tomorrow, kids time

odd, you can try rm .lsp/.cache and reload your editor

it seems it works if the thing is fully qualified ex: if I type (clojure.string/incl|) it will autocomplete, but my require alias gets no completion

fully qualified names on a defn in my own project fails tho (in another ns)

clojure-lsp --version clojure-lsp 2021.10.20-13.04.11 clj-kondo 2021.10.19

did rm ./.lsp and ./.clj-kondo

more context: https://gist.github.com/mpenet/ba30b42616e8a914f4464f693a46b820

if I type (s/|) autocomplete pops saying s is a Property (it's an alias to clojure spec in that case), but nothing gets completed on it

and my emacs config so you have a complete picture : https://github.com/mpenet/emax/blob/master/init.el#L486-L505

I keep trying messing with various things but I can't make it work

another clue: if clojure.spec.alpha is required it breaks all completion on (clojure.spec.alpha/|)

if not required completion on it works

same with my own code, or an exernal lib on the classpath, once required completion on it fails

oh! https://gist.github.com/mpenet/3d39800d0d02e0e22e5fa610fc572a19

well the nrepl server fails to start, there's that

added nrepl+cider-nrepl to classpath just to test, the error goes away but completion behavior is still the same

still broken with clojure-lsp mater

and now it works, not sure what fixed it. I rm'ed my .emacs.d/straight/* files and copied your .lsp/config.edn. About the straight part, I did do a straight-pull-all before all these tests, so I am not sure what's different

same pinned version of all repositories in straight too, a real mistery. In any case, sorry about the noise 🙂 at least I got to learn how to work-on /debug clojure-lsp

next:

without having a repl running everything is fine

when cider jacked in, completions go away

describe-var on lsp-enable-completion-at-point -> t

(add-hook 'cider-mode-hook (lambda () (remove-hook 'completion-at-point-functions #'cider-complete-at-point))) ; use lsp

from your conf heh

Yeah, cider completion mess up with lap one unless you add that :/

well for some reason with these config changes I lost clojure.core/* completions

only in the current ns I am working on, maybe something fishy that lsp doesn't like on it

try not using cider on the proejct until we understand what is the issue

I am not right now

it's weird, completion on core works at the end of the ns (after a bunch of code), not right after the ns declaration

so same buffer

it completes all the other stuff tho (clojure.specs & co)

killed the session, re-opened and now it works

odd, if you manage to reproduce again feel free to open an issue with a sample repro where I can try

will do

@U9V9M9MFZ this sounds like wrong workspace configured in your lsp-mode

could you try lsp-workspace-folders-remove , and remove any wrong folder, like your home and the clojure-lsp project

and then M-x lsp and select the correct project root for clojure-lsp

Yes, that did the trick - thank you very much 🙏 ! Indeed my home folder had to be removed along with some clojure folders - don’t know how they ended up there, I have never called lsp directly, I have it starting when I visit a clojure namespace. Anyways, thanks again!

good :) that's a common issue on lsp-mode

ah I see, noted!