This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-27
Channels
- # beginners (43)
- # boot (1)
- # cider (7)
- # cljdoc (10)
- # clojure (110)
- # clojure-boston (1)
- # clojure-finland (2)
- # clojure-italy (19)
- # clojure-losangeles (1)
- # clojure-new-zealand (1)
- # clojure-nl (4)
- # clojure-spec (34)
- # clojure-uk (163)
- # clojurescript (136)
- # code-reviews (1)
- # component (13)
- # cursive (18)
- # datomic (99)
- # emacs (14)
- # events (4)
- # fulcro (14)
- # hoplon (15)
- # hyperfiddle (3)
- # jobs (3)
- # jobs-discuss (1)
- # lein-figwheel (10)
- # onyx (1)
- # pedestal (8)
- # re-frame (5)
- # reitit (4)
- # rum (1)
- # shadow-cljs (317)
- # spacemacs (24)
- # specter (9)
- # sql (2)
- # tools-deps (6)
- # yada (3)
is add-lib
likely to get officialized anytime soon?
Define soon
I’m seeing 2 definitions: 1) in or after a short time. 2) used to indicate one’s preference in a particular matter. but more interesting, the origin: Old English sōna ‘immediately.’ 😛
notes on git deps with clj
https
with authentication is not supported yet by clj
(https is 65% of github's traffic)
ssh
authentication via Java is a usability trashfire (some KEX methods unsupported)
The terminal is not interactive in clojure
, so you cannot accept unseen public host keys - this might be ok, but surprising.
Esoteric .ssh/config
options can break cloning because the underlying java ssh libraries misread the .ssh/config file
ed25519 keys supported via ssh-agent, but not via ~/.ssh/config entries
Porting to shell out to git
would help all of these issues, if remains compatible with Windows support