This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-19
Channels
- # announcements (14)
- # babashka (16)
- # beginners (81)
- # calva (18)
- # chlorine-clover (8)
- # cider (4)
- # clj-kondo (11)
- # cljdoc (4)
- # cljsrn (5)
- # clojure (163)
- # clojure-europe (30)
- # clojure-nl (3)
- # clojure-spec (7)
- # clojure-uk (4)
- # cursive (3)
- # emacs (12)
- # events (1)
- # figwheel-main (3)
- # fulcro (60)
- # introduce-yourself (3)
- # jackdaw (12)
- # juxt (3)
- # lsp (77)
- # malli (23)
- # mid-cities-meetup (9)
- # music (2)
- # off-topic (12)
- # portal (6)
- # releases (2)
- # shadow-cljs (3)
- # spacemacs (7)
- # sql (1)
- # tools-deps (2)
- # vim (3)
Loving the LSP status improvements in VS Code (is that a new Calva feature?)
It actually has a percentage on emacs and vim, but I could not make it work for vscode 😔
(i've searched the google and the slack archives, and i didn't see this question raised)
how do i resolve this error, when trying to use lsp-format-buffer
? i figure i need to get cljfmt set up somehow, but i'm not finding any instructions about it.
Error: (lsp-capability-not-supported "documentFormattingProvider")
it may have resolved itself after a restart!
or, rather, the formatting is working, but i'm also seeing this error message
the only thing i do after hooking lsp is to set these two:
lsp-lens-enable nil
lsp-signature-auto-activate nil
lsp-enable-identation
is 'void' when i evaluate it in an .el (i'm not a big emacs lisp person so if that's the wrong way to check, apologies)
hum, that's weird, maybe some bad compiled lsp-mode package. Do you use some emacs framework like doom or spacemacs?
no, it's actually mega simple! https://github.com/robert-stuttaford/.emacs.d
I mean, even with your config, the packages are compiled and I stayed somewhere, right?
apologies, i don't want to waste your time, @UKFSJSM38 - let me regroup, and see if i can be clearer about what i'm seeing 🙂
Interesting. Every once in a while my emacs freezes completely (the UI doesn't redraw, cpu usage is minimal), C-g
does nothing so I need to sigkill it. It happened again, but this time I decided to try what happens if I kill clojure-lsp
-> emacs got unstuck and works again. Sadly there's nothing interesting in the clojure-lsp
log file or the various lsp
buffers in emacs 😞 I assume this is an issue with lsp-mode
rather than clojure-lsp
?
yeah, I'm browsing through existing issues right now, just in case I'm not the first to notice this
I think 90% of the time this happens after I've just created a new .clj
, .cljs
, or .cljc
file and I'm in the process of adding various (:require [foo.bar])
statements into the ns
form.
@U0178V2SLAY are you by any chance using potemkin in your project?
there was an issue fixed in clj-kondo 2022.01.15 which had a circular reference problem with one of the deps, some ring-http-response library
could be that. you can check that by linting your classpath on the command with an older version of clj-kondo
We actually are using potemkin (or at least our project has it, I don't personally use it in my code). But I'm also pretty sure I'm using the latest clj-kondo. My morning routine is to always check for a new version of kondo or lsp 🙂
good point 👍
so it would be worth checking using clj-kondo equal to the version in lsp, on the command line
good thing I have a babashka script to re-initialize the kondo cache, I'll try tomorrow and report back
Maybe @U0178V2SLAY can test a pre-release from CI
@U04V15CAJ how hard would be to make that binary available in a channel just like kondo?
but I have something even better now: https://github.com/babashka/babashka-dev-builds every master build gets posted over there and you can even install it using the normal install script
sure, I can be your guinea pig. but I'm not certain how easily I can reproduce my original issue. I've also previously built & used lsp locally when testing some earlier problem I think
but I'll at least try that linting trick wrt. potemkin
Just concurring with the above to add one more data point. Emacs occasionally freezes and does not unfreeze until killing clojure-lsp, as mentioned above. One tendency I've noticed is that it appears to occur when switching git branches and the underlying code changes, but I'm not sure about that.
Hi.
i just tried the new clojure-lsp version to 2022.01.03-19.46.10
from github action but it failed over.
Run clojure-lsp clean-ns --dry
[ 0%] clojure-lsp
[ 5%] Finding kondo config
[ 8%] Finding project specs
[ 10%] Finding cache
[ 15%] Discovering classpath
Error: Classpath lookup failed when running `lein classpath`. Some features may not work properly. Error: Retrieving com/github/clojure-lsp/lein-clojure-lsp/0.1.0/lein-clojure-lsp-0.1.0.pom from clojars
it seems lein classpath
is failing to download one of your dependencies, in this case lein-clojure-lsp
😛
also this jar has thousand of downloads, it sounds like some issue with your lein or project
It looks it run ok with my project from 2021.12.01-12.28.16 but any posterior versions it failed the same way. I think its because it parse something from the deps of my project before running lein classpath