Clojurians Log v2

1. That feature is called https://clojure-lsp.io/features/#semantic-tokens, basically with better understanding of what each token is, clojure-lsp can color it better since it knows if it's a var or a symbol etc, usually it helps and most people like this feature, you can disable via lsp-semantic-tokens-enable .

ah yes, I just want to keep those regular variables white 🙂

2. unresolved-var here means, it found the alias, but that var format is unknown, is that really correct?

it's not unknown I can jump to it

Is the var defined in a special way?

it's defn format in honeysql

Can you wipe .clj-kondo/.cache and restart LSP ? Perhaps it will help

oh wait it might be old honeysql

but it's a defn, not a macro

If it persists repro in the form of a github repo welcome. Also try linting from the command line to see if you get the same issue

alright removing the cache solved it, good to know

only color of letters i would like to change and then i am converted

If you still have the cache make a backup, I can try to inspect what’s in the transit file… too late. ;)

haha sorry

thanks for the help!

I tried registering new client like so:

(lsp-register-client
     (make-lsp-client
      :new-connection (lsp-stdio-connection "basedpyright")
      :activation-fn (lsp-activate-on "python")
      :server-id 'basedpyright))

[2025-04-23T19:17:52Z INFO  emacs_lsp_booster::app] Running server "/Users/ag/.local/share/mise/installs/python/3.11.12/bin/basedpyright"
[2025-04-23T19:17:52Z INFO  emacs_lsp_booster::app] Will convert server json to bytecode! bytecode options: BytecodeOptions { object_type: Plist, null_value: Nil, false_value: Nil }
thread '<unnamed>' panicked at /github/workspace/src/app.rs:145:18:
called `Result::unwrap()` on an `Err` value: Server->client read thread failed

Caused by:
    Invalid header format
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Process basedpyright stderr finished

unfortunately, I didn't try yet lsp-bridge so not sure exactly what's your problem but your error looks like some ser/deser issue with json which is weird

I'll figure this out, right now I just can't figure out how to properly register new client. Python just refuses to use it

it keeps saying: LSP :: The following servers support current file but do not have automatic installation: basedpyright. something todo with :new-connection key in make-lsp-client. Just can't figure out the correct incantation for it

Holy swiveling motherducking flapdoodles. This turned out to be such an imbecilic waste of time. Check this out. The only reason why I went on a tangent of "fixing my lsp setup for Python", is because lsp-format-buffer stopped working, telling me that the server "doesn't support that feature". I started investigating and found out that despite lsp-pyright-langserver-command being set on (pip-installed) "basedpyright", it still tries to npm install pyright server. And lsp-describe-session indeed says it's running pyright. So that convinced me that pyright doesn't support the feature. But it worked before, so then I guessed that for whatever reason, it switched to pyright. I spent hours trying to figure out why it's not connecting to basepyright. After figuring out how to create my own custom client, explicitly set on basepyright, I tried formatting python buffer, and I was shocked to see that this one doesn't support it either. Turns out, neither of them support that feature, and I used to have "ruff" (which lsp-mode connects to for formatting and linting), and when I was dealing with conflicting python dependencies in a project, I accidentally removed it. I didn't have to do all that shit — trying to figure out lsp-pyright; then switching to lsp-bridge, which fucked up my regular lsp keybinds and doesn't properly register a client; then trying to make a new client, etc. I just needed to reinstall ruff. And stupid lsp-pyright still npm installs pyright, even when I told it to use basedpyright. And I'm still honestly confused, which one is it using. Why does it need pyright node package at all? And how do people use format-buffer feature when using eglot, which afaik doesn't support multiple servers simultaneously. This shit is so stupid and confusing for no real reason - multiple lsp-server choices for Python and none of them are truly painless and nice; many different linters, but how do they even differ? Why can't an lsp-server just call a linter directly? And I haven't even yet started writing any serious Python. Really makes me appreciate the consistency and pragmatics of clojure-lsp.

darn... how do I use .venv bullshit in eshell now?... sigh... upd: found mise.el, worked like a charm. Fucking Clojure. Turn me into a delusional programmer. I forgot that "real-world programming" is a bunch of shit not working for some arbitrary and stupid reasons and that is "normal" and "business as usual". Why the fuck when something breaks in Clojure, at least it feels it's breaking for some observable, practical reasons, not for some fiddlesticks made of horseshit?