This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-06
Channels
- # babashka (19)
- # beginners (68)
- # calva (9)
- # cider (27)
- # clj-kondo (64)
- # clj-on-windows (2)
- # cljdoc (8)
- # clojure (11)
- # clojure-europe (58)
- # clojure-italy (1)
- # clojure-nl (23)
- # clojure-uk (5)
- # clojurescript (9)
- # cryogen (18)
- # cursive (14)
- # data-science (17)
- # emacs (6)
- # gorilla (6)
- # graphql (1)
- # gratitude (2)
- # holy-lambda (10)
- # introduce-yourself (1)
- # jackdaw (3)
- # jobs (1)
- # leiningen (2)
- # malli (3)
- # missionary (33)
- # off-topic (21)
- # pedestal (7)
- # polylith (8)
- # quil (3)
- # random (1)
- # releases (1)
- # remote-jobs (7)
- # shadow-cljs (18)
- # specter (1)
- # sql (8)
Wondering… Having had reasons to use my Windows machine today to fix some Calva issue I again notice that still can’t get the clojure
command to work. I use deps.clj
instead and that one works great. Does it make sense to replace the current different scripts with deps.clj
instead? I think so. Written in Clojure is one good reason. And since there is a fast starting binary available as well, the scripts do not have that advantage either. I know of only one problem still remaining for clj-on-windows using deps.clj
and that is an Oracle Java executable bug munging quotes in command line arguments that Oracle has fixed in newer versions. (That problem is shared between the current PS module and deps.clj.)