Any chance I can get some feedback from the LSP team here: https://github.com/clj-kondo/clj-kondo/issues/1112#issuecomment-756380648 ?
I think @snoe has more context on that clj-kondo code indeed 😕
Is clojure-lsp supposed to work for babashka scripts?
I can see it having trouble with deps that are built into bb, so there is no deps.edn for it
but clj-kondo doesn't care about deps, they are optional to lint, it won't try to find them anywhere unless you lint those yourself
The clj-kondo extension helps me nicely with the script. Calva with clojure-lsp does not seem to do anything at all.
And since babashka doesn’t support cider-nrepl I have a less than stellar experience. 😃
> And since babashka doesn’t support cider-nrepl it does support nrepl though?
Yeah, that’s awesome. Only takes me so far though.
I was hoping clojure-lsp would close some of the gap.
What is it from cider-nrepl that you would like to have in bb nrepl?
Anyway, it would be great if LSP could support bb scripts ;)
The ones that Calva use 😃 . In some order of preference for my own workflow:
1. info
2. complete
3. stacktrace
4. init-debugger/debug-input
5. test-var-query/retest/test-stacktrace
@pez The complete
op should work in the nREPL
@borkdude lgtm I'll get as far as possible without str... I've got a couple more fixes in the pipe that were missed in locals and name pos too..
@snoe I just wondered: when using a local, it's always the same as the name, there isn't a syntactical change possible, right?
This is why it didn't seem necessary to me
In fact it does. I think it might be missing some metadata, so it looks like a regular word match in vscode.