lsp

lread 2025-09-28T21:05:26.968409Z

My good friend clojure-lsp is borked (not in the good borkdude way). I always appreciate clojure-lsp, but one can forget how much one benefits from something until that thing is gone. gratitude I'll likely eventually figure it out, but is anybody else having issues on doom emacs?

borkdude 2025-09-28T21:20:35.490949Z

Have you tried turning it off an on again?

lread 2025-09-28T21:30:49.779139Z

Ha! You just made me laugh out loud. simple_smile

😆 1
lread 2025-09-28T21:45:26.249059Z

And I'm still smiling, thanks. This mirth is a soothing balm for my current clojure-lsp plight.

borkdude 2025-09-28T21:46:30.914969Z

So any error messages or so?

👀 1
lread 2025-09-28T23:01:33.481619Z

Yeah, afk now, but I'm getting messages that lsp server doesn't support much of anything. Renaming, reformatting, etc. I'm guessing some doom emacs issue. @ericdallo are you running latest doom emacs?

ericdallo 2025-09-28T23:14:27.371319Z

Not really, but I just recall that I faced the same thing with latest doom a week ago when I bumped doom

ericdallo 2025-09-28T23:14:43.351879Z

I didn't have time so I rolledback

ericdallo 2025-09-28T23:15:10.970129Z

But glad you are having the same issue 😅 we can investigate, probably something on my config or doom

👍 1
lread 2025-09-30T13:48:31.496659Z

Ok, gonna try the bisect thing, I'll letcha know how it goes.

lread 2025-09-30T16:10:31.023139Z

Alrighty! On September 14, 2025, https://github.com/doomemacs/doomemacs/commit/5a9a2f4e18c2952d9d10b46dcb52fcde97b2521d broke things for me. If I follow the advice on how to undo in the commit message:

This will supposedly make lsp-mode more memory efficient. It will only
take effect the next time lsp-mode is rebuilt/reinstalled.

It can be undone with this added to $DOOMDIR/packages.el:

  (setq lsp-use-plists nil)
Then my doom-emacs doom emacs now works again with clojure-lsp clojure-lsp! 🎉

lread 2025-09-30T16:16:31.494289Z

I brute-forced a full doom emacs rebuild via:

rm -rf ~/.config/emacs/.local
doom install
doom sync
Likely overkill, but I wanted no lingering mysteries and a clean slate.

ericdallo 2025-09-30T16:34:25.338009Z

ahh got it! lsp-use-plists was something we added to lsp-mode years ago, which improves a lit bit performance, but never worked with my config for some reason, I think this makes sense now hehe

ericdallo 2025-09-30T16:34:50.438339Z

I will take a look how to fix that for my config, it must work, thank you very much for the finding @lee!

👍 1
lread 2025-09-30T17:31:57.852229Z

All you should need to do is add the following line to your .config/doom/package.el :

(setq lsp-use-plists nil)

👍 1
lread 2025-09-30T17:32:27.337089Z

(and then rebuild)

ericdallo 2025-09-30T19:17:44.183199Z

@lee I just bumped doom to latest + lsp-mode as well and it worked only after setting lsp-use-plists to t , I rebuilt-in lsp-* packages as well 🤷‍♂️

lread 2025-09-30T19:30:16.040169Z

Huh! That is weird that (setq lsp-use-plists nil) did not work for you. Isn't t https://github.com/doomemacs/doomemacs/blob/5e7e93beb9f2b5a81768aaf4950203ceea21c4f6/modules/tools/lsp/packages.el#L18?

ericdallo 2025-09-30T19:33:20.473819Z

yes, it is, but I use as nil for years 😅 mostly because lsp-dart issue, but I will take a look at lsp-dart later

ericdallo 2025-09-30T19:33:42.468189Z

i believe doom broke something for users that use lsp-use-plists nil....

lread 2025-09-30T19:34:48.266549Z

Yes, something around that, I suppose. But for me, clojure-lsp was broken when the value was t.

lread 2025-09-30T19:35:27.659849Z

My doom config is based on yours but, of course, not identical! So there must be some other significant differences.

ericdallo 2025-09-30T19:36:19.351989Z

weird, I just pushed changing to t since now it works with latest

ericdallo 2025-09-30T19:36:23.423519Z

but yeah, interesting

ericdallo 2025-09-30T19:36:27.113859Z

thanks for the help so far

lread 2025-09-30T19:37:09.643939Z

We still have a mystery. But at least Doom Emacs latest is working for both of us now!

🎉 1
lread 2025-09-30T20:03:27.352069Z

And, as always, @ericdallo, thank you for clojure-lsp, it is truly AWESOME!

ericdallo 2025-09-30T20:03:56.657519Z

💜 Glad you like it! the community made it awesome!

1
rolt 2025-09-29T15:18:45.402259Z

I had tons of wrong-type-argument hash-table errors on lsp--on-notification when analyzing the project this morning. Rolled back for the day. I've once again updated everything at the end of the day and now everything works... Elisp native compilation cache issue maybe ?

👍 1
borkdude 2025-09-29T15:19:39.434729Z

@rolthiolliere yes, that happened to me too a number of times

ericdallo 2025-09-29T15:22:06.175979Z

Yeah, to debug those things, clean cache is a must

ericdallo 2025-09-29T15:22:38.668939Z

I may have time to check that next week @lee in case you don't check it before

lread 2025-09-29T16:06:21.831729Z

Thanks @ericdallo, although I have some talents, diagnosing emacs is not one of them yet! I'm going to try rolling back doom emacs to see if that works. I did also upgrade emacs to 30.2 recently-ish, maybe I built it with some option that is problematic to the current doom emacs.

ericdallo 2025-09-29T16:45:01.009499Z

NP! I'm using 30.2 as well, but 30.1 was having issues as well, we should probably do a git bisect