the config dir is determined from the following info (the "user" deps.edn): https://clojure.org/reference/deps_and_cli#deps_sources

I suspect you have $XDG_CONFIG_HOME set

yes

so you can override by setting CLJ_CONFIG

I saw this, but haven't understand

Is it problem of Cursive or Clojure?

that's an environment variable, so you'll want to export a new setting wherever you do things like that, in such a way that Cursive sees the effects of that

Cursive can either use the clojure CLI or use an embedded library (tools.deps). In both cases, those use the described environment variables

as I understand clojure know what is "config-dir". Why Cursive can't see it?

I don't understand, sorry

from the original post, you said you wanted to change the config dir - you do that by setting environment variables

Result of clojure -Sdescribe is

:config-dir "/Users/jurko/.config/clojure"

what problem are you seeing?

but for Cursive config dir is /Users/jurko/.clojure

ok, I would guess that at the terminal, you have $XDG_CONFIG_HOME set, but that Cursive is not seeing that environment variable due to how it is configured or started

you can check that by doing something like (System/getenv "XDG_CONFIG_HOME") at a repl in Cursive

so then the question is how to set environment variables in a way that Cursive sees them - I don't know the answer to that, but it probably depends on how you start it

Thank you.

Following @U064X3EF3 suggestion, I've check at local and remote repl:

well in the remote case, you're checking the environment of the remote jvm, so not sure that's relevant

Remote does see variable, local - doesn't

you can set env vars in the run config

In Cursive, you can use Preferences | Build, Execution, Deployment | Build Tools | Clojure Deps | Project Settings | Path to config directory