This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-08-27
Channels
- # announcements (10)
- # bangalore-clj (1)
- # beginners (130)
- # calva (8)
- # cider (66)
- # circleci (2)
- # clojure (197)
- # clojure-europe (2)
- # clojure-italy (8)
- # clojure-nl (5)
- # clojure-spec (14)
- # clojure-uk (35)
- # clojurescript (46)
- # code-reviews (5)
- # cursive (4)
- # datomic (88)
- # duct (1)
- # emacs (2)
- # figwheel-main (15)
- # fulcro (20)
- # graalvm (1)
- # graphql (3)
- # jackdaw (2)
- # leiningen (2)
- # off-topic (64)
- # pathom (53)
- # re-frame (52)
- # reagent (12)
- # reitit (43)
- # rewrite-clj (1)
- # shadow-cljs (38)
- # spacemacs (3)
- # sql (17)
- # tools-deps (6)
- # vim (30)
Has anyone else noticed a change in how Spacemacs handles exec-path? It used to somehow pick up the value in the PATH environment variable and use that as the exec-path, but it doesn't appear to be doing that now. I'm on MacOS, if that's relevant.
Interestingly, when I C-h v exec-path it shows:
exec-path is a variable defined in ‘C source code’.
Its value is
…
Original value was
…
PATH, which is what I want. I guess that means it's getting overwritten somehow? :thinking_face:I found this, but (shell-command-to-string "env") shows the right thing. https://github.com/syl20bnr/spacemacs/issues/10906