This is kondo’s config

Can you make a clj-kondo only repro that I can clone locally so I don’t have to copy or type code from screenshots? Then I’ll have a look later today

I don’t get this error in a new project, so I won’t even upload it. The definition in malli-types-clj/config.edn is same for both projects. I tried to delete clj-kondo .cache and also .lsp from the original project, no luck. Unfortunately I can’t share the original project and it is really complex, so there are a lot of variables. Do you have any idea where I could look?

If you can't make a repro, I can't help you fix it, unfortunately, but maybe you can downgrade malli and ask in #CLDK6MFMK - seems like a downstream problem

Interesting, the downgrade didn’t help. So I thought to delete .clj-kondo/metosin and it worked (with old and new version as well).

https://github.com/metosin/malli/issues/865 here's the bug you ran into

that's a demonstration of "show docs" called on ->violation displaying the docs for this whole top-level form

is there a better way to do this?

if I switch the hook to (api/token-node 'defrule) instead of 'def , then go to definition and show docs work but the whole form has an "unresolved symbol: sorted-rules-require" error

Why write such a macro in the first place? Maybe ^:dev name could also work?

regardless of that, let's take a look at your hook code

🤷 it's the api i've decided on, it's shortest and simplest and communicates the intentions

This is wrong:

(list* (api/token-node 'def)
                                   (api/token-node (symbol (name (api/sexpr rule-name))))

list* expects the last thing to be a collection of nodes

I have "body" at the end, doesn't that expand properly?

I recommend using (println node) before you return it, and then execute this on the command line

then you will see what I mean probably

oh yes, body, I missed that

I think you can fix stuff by preserving more original locations via the metadata

with with-meta or vary-meta

(defn defrule-hook
  [{:keys [node]}]
  (let [[defrule rule-name & body] (:children node)
        new-node (api/list-node
                   (list* (with-meta (api/token-node 'def) (meta defrule))
                          (with-meta (api/token-node (symbol (name (api/sexpr rule-name))))
                                     (meta rule-name))
                          body))]
    {:node (with-meta new-node (meta node))}))

there we go, that works

thank you for the help

Is it possible to create a repro repository?

Are you running clojure-lsp or do you also run clj-kondo separately somehow?

I could make a repro repo, but I think the issue is much deeper. I’ve gone into the repro repo I sent you when I had issues with defn-spec. It doesn’t work. I’ve messed something up at the global/emacs config level or something else deeper in the well than the project. That’s why I’m a little lost as to how I should continue

the first thing I usually recommend people to try it clj-kondo on the command line

are you able to run this:

clj-kondo --lint src

It lints

and maybe clojure-lsp as a command line tool:

clojure-lsp diagnostics

It gives me an output similar to linting filled with how not perfect my code is

in your emacs config folder, can you maybe do this: mv elpa elpa.bak

and then restart your emacs

I’m assuming that’s the same as moving my straight repos folder.?

I guess so. This reminds me. #CPABC1H61 has a minimal emacs config to debug things

you could try that one. @UKFSJSM38 knows where it is probably

https://clojure-lsp.io/troubleshooting/

Yes, and if it's a problem with not even starting clojure-lsp check this https://emacs-lsp.github.io/lsp-mode/page/troubleshooting/

Lsp starts, the server info gives me a clojure-lsp version of 2.27, and lsp of 2.17, the classpath settings is nil.

scratch that, clj-kondo of 2.17

I think both versions are wrong, they should be dates

Yes, I was referring to the dates, feb 17th and 27th

I can’t copy the server info, because I’m not sure how to open it in a proper buffer.

go to *Messages*

You can just click the mini buffer or do what borkdude said

Duh, not a proud moment

:client-settings
 {:dependency-scheme "jar",
  :show-docs-arity-on-same-line? true,
  :text-document-sync-kind nil,
  :source-paths nil,
  :source-aliases nil,
  :cljfmt-config-path ".cljfmt.edn",
  :document-formatting? true,
  :document-range-formatting? true},
 :project-root-uri "file:///home/pat/m",
 :port "NREPL only available on :debug profile (`bb debug-cli`)",
 :project-settings {},
 :server-version "2023.02.27-13.12.12",
 :clj-kondo-version "2023.02.17",
 :log-path "/tmp/clojure-lsp.3157811663365747466.out",
 :classpath-settings nil}
 :client-settings
 {:dependency-scheme "jar",
  :show-docs-arity-on-same-line? true,
  :text-document-sync-kind nil,
  :source-paths nil,
  :source-aliases nil,
  :cljfmt-config-path ".cljfmt.edn",
  :document-formatting? true,
  :document-range-formatting? true},
 :project-root-uri "file:///home/pat/m",
 :port "NREPL only available on :debug profile (`bb debug-cli`)",
 :project-settings {},
 :server-version "2023.02.27-13.12.12",
 :clj-kondo-version "2023.02.17",
 :log-path "/tmp/clojure-lsp.3157811663365747466.out",
 :classpath-settings nil}

Everything looks good, check if project-root-uri really matches your project root

It does. I’m doing a proper full on reinstall of my emacs deps as borkdude outlined. It feels like I must have messed something up with my emacs config, but for the life of my I don’t remember touching it.

@U036UJBDM5G I don't want to sound patronizing, but do you save your emacs config in version control? I even save my entire elpa directory in version control since 2013 haha

I have all my configs, but I git ignore my autodownloaded deps.

I've had too many weird issues before that and decided to do it the blunt way

If that turns out to be my problem, I may jump on that ship.

I'm not using straight.el etc, it may have better version management

It supposed to immutable like nix, but all I know is I just add :straight t to my use-package and it works.

I've had issues with .elc files before, when I removed those, emacs re-compiled the .el files and suddenly a problem was fixed

The same has happened with straight many times. This time I deleted andything with clojure in the name and it didn’t help, but it costs nothing to go further.

@UKFSJSM38 what was the minimal emacs project to install clojure-lsp / lsp-mode again? it helped me find the weird delay problem at the time

https://emacs-lsp.github.io/lsp-mode/page/troubleshooting/#check-if-any-package-or-wrong-config-could-be-causing-the-issue

ah yes, @U036UJBDM5G you could try that file instead of init.el and see if you can get things working

Well, no dice on the rebuilding emacs with fresh packages, and no dice on the minimal config.

is clojure-lsp on your path, can emacs find it?

else lsp-mode will download it anyway right

I appreciate you both for coming out. HMU if you think of anything. I’m a frustrated dog, so maybe my dog and I should go outside for a walk with the beautiful weather we’re having. When I come back, I’m installing clojure-lsp and clj-kondo from source again, and launching with a custom command. That worked in the past. clojure lsp is there it just doesn’t seem to link with emacs, emacs knows it’s there, it knows my classpath. The problem lies somewhere in the middle.

enjoy

A simple project usually helps a lot debug such issues, I recommend testing with my http://github.com/ericdallo/clojure-sample project

@U04V15CAJ @UKFSJSM38 Thanks for all the help. After no luck with building from source. I went nuclear rm -rfed the f out of everything I could find, then I reinstalled things just like the readme brought my custom config back in piece by piece. I wish I had something smart to say… I’m just happy I can use my tooling again. Side note, I’ve grown way to reliant on tooling to be comfortable. Keep up the good work. I appreciate the quality things you make.

Thanks! Glad it works now :)