This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-11-10
Channels
- # announcements (1)
- # beginners (2)
- # calva (41)
- # cider (3)
- # cljdoc (2)
- # cljs-dev (23)
- # clojure (94)
- # clojure-dev (23)
- # clojure-russia (5)
- # clojure-spec (9)
- # clojure-uk (85)
- # clojurescript (94)
- # code-reviews (1)
- # cursive (5)
- # datomic (1)
- # emacs (8)
- # figwheel (1)
- # figwheel-main (10)
- # fulcro (27)
- # graphql (11)
- # hyperfiddle (1)
- # jobs-discuss (10)
- # kaocha (3)
- # luminus (7)
- # lumo (1)
- # off-topic (85)
- # onyx (1)
- # pedestal (1)
- # re-frame (3)
- # shadow-cljs (21)
- # tools-deps (1)
- # yada (6)
Thanks to all involved in making Cider an amazing tool for Clojure development. I use Cider every day for work and personal projects and find it it invaluable. I am excited about the changes you are making to Cider and all the work everyone is putting in to make it even better. Thanks for continuing to update the docs so I am aware of any significant changes to the way Cider works. I use Cider via Spacemacs develop
which pulls down the latest version of Cider, so I always go and look at https://github.com/clojure-emacs/cider/commits/ before an update to know what I am getting. Nothing has broken for me in the last couple of years and I could easily roll back a package update if it did. Thanks again
I too use CIDER every day and find it invaluable. Like most people I guess, I've had problems in the past with updates to packages breaking things. Now I keep my entire Emacs config (including my .emacs.d directory) in a Git repo, so I can easily get back to a good state. An added bonus is that this makes it easy to get the same Emacs setup on multiple machines.