I have this in my .el stuff:

lsp-enable-file-watchers nil
      lsp-file-watch-threshold 10000

they might not make sense in combination, but that's what I have ;)

ah right so you just disabled it then though

I guess I can do the same

not entirely sure what does that affect

lsp watches all files by default. if you have a js portion of your project, this means it will watch a ton of temporary files and compiled output. Currently there’s no way to specify the folders you want it to watch, you have to enumerate the ones you want it to not watch

(although it’s been a while since i’ve looked into it)

https://github.com/emacs-lsp/lsp-mode/pull/1829

It's been years since I used a Mac but I used to run into the default file open limit on all sorts of things so I used to set ulimit to unlimited. I don't remember the command or config for that any more but if you search for too many open files ulimit I expect you can find it...

Since you use emacs, you might be interested in https://emacs-lsp.github.io/lsp-mode/page/faq/#how-do-i-force-lsp-mode-to-forget-the-workspace-folders-for-multi-root-servers-so-the-workspace-folders-are-added-on-demand (to make lsp lazily load workspaces and hence file-watches). Adding ignores to compiled output also helps (I have it set for .projen, cdk.out , .next, .husky, etc)

https://github.com/clojure-lsp/clojure-lsp/commit/65f06f218a72bd2d19ce881d33e4f1fc09f62b59 seems to say "yes"

Definition should be supported, references I guess, needs to test

but when I try something like

(def foo "hello")

(def bar 'the.current.namespace/foo)

it's possible to support, but probably needs some tweak

right, ok. I can make a ticket if it helps 🙂 motivation: we have a bunch of datastructures with symbols (e.g. (def operations {"some name" 'some.namespace/a-function ...}) + requiring-resolve) and unfortunately clojure-lsp flags the referred vars with "unused public var", which is sometimes unfortunate as you might accidentally think it's safe to remove such var.

Hum, my biggest concern is flag it as used wrongly

But I can see how convenient it is most of the time

Please open a issue

Is this sufficient? https://github.com/clojure-lsp/clojure-lsp/issues/1804

yes, thanks!