Eric Dallo

@snoe `cd /Users/case/dev/lsp/cli && clj -M:debug:run` should add the debug profiler

I think it's valid to add a `make run-debug`

Amazing deep dive @mainej, really glad you took the time to check each feature and how that would behave, thanks for that. I like lazy analysis as AFAIK is the...

> But at first a flag will be useful. As clojure-lsp developers we can use it and maybe ask the community to test it as an "experimental" feature. After we're...

> First, though we ask for the neighbor files to be re-analyzed and re-linted, we don't actually need them to be analyzed. They haven't changed, so their analysis will be...

> A big thing that I think we've gone away from is picking up changes from the filesystem. It is very important that if you git pull new files that...

## About problem 1 > It takes slightly less than 1 minute to become interactive, about 3/4 analyzing. (And again, there's an additional 2 minutes publishing diagnostics.) This was actually...

@mainej did some double check and it turns out we already save the `:settings :source-paths` absolute. We just don't absolutize the ones on classpath but when we use/check we do....

I see, probably it's related with projects with multiple classpath sources like deps.edn + shadow-cljs

It seems to be related with custom source-paths declared by user, when clojure-lsp merge the refreshed settings it considers both relative and abs :(