This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-12-09
Channels
- # adventofcode (93)
- # announcements (11)
- # babashka (7)
- # babashka-sci-dev (17)
- # beginners (73)
- # biff (7)
- # calva (3)
- # cider (1)
- # clj-kondo (160)
- # clj-together (12)
- # clojure (44)
- # clojure-art (2)
- # clojure-europe (12)
- # clojure-losangeles (1)
- # clojure-nl (3)
- # clojure-norway (22)
- # clojure-uk (2)
- # clojurescript (8)
- # clr (1)
- # cursive (6)
- # data-science (1)
- # datomic (1)
- # emacs (6)
- # events (1)
- # exercism (1)
- # fulcro (6)
- # graphql (2)
- # introduce-yourself (1)
- # lsp (18)
- # nrepl (7)
- # off-topic (45)
- # polylith (25)
- # portal (25)
- # practicalli (3)
- # re-frame (14)
- # reagent (28)
- # reitit (2)
- # releases (2)
- # shadow-cljs (73)
- # sql (11)
- # tools-deps (12)
- # transit (4)
- # xtdb (4)
I wonder if I set my XDG_HOME env var to .config as suggested https://github.com/practicalli/clojure-deps-edn#install-practicalli-clojure-deps-edn if that will affect where other programs on my Mac will look for config files??
I assume setting XDG_CONFIG_HOME
will have an effect on any program that look for that environment variable. Not all applications do.
The worse case is that a new configuration file is created for a program in .config/
If there is an existing program config n the $HOME
directory, it will still be there. It will be down to an individual program as to if it also checks $HOME
first, before creating something in XDG_CONFIG_HOME
https://practical.li/blog/posts/adopt-FreeDesktop.org-XDG-standard-for-configuration-files/ shows the experiences I had moving to the XDG standard, which has been very positive in my view