This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-03-14
Channels
- # aleph (2)
- # atlanta-clojurians (5)
- # beginners (38)
- # boot (2)
- # bristol-clojurians (1)
- # cider (31)
- # clara (8)
- # cljs-dev (136)
- # cljsrn (4)
- # clojure (86)
- # clojure-china (1)
- # clojure-greece (1)
- # clojure-italy (24)
- # clojure-nl (1)
- # clojure-spec (21)
- # clojure-uk (19)
- # clojurescript (68)
- # community-development (28)
- # core-async (35)
- # core-logic (4)
- # cursive (1)
- # data-science (1)
- # datascript (1)
- # datomic (46)
- # events (1)
- # figwheel (6)
- # fulcro (11)
- # graphql (3)
- # hoplon (1)
- # jobs (6)
- # jobs-discuss (94)
- # keechma (3)
- # luminus (4)
- # lumo (7)
- # mount (6)
- # off-topic (24)
- # onyx (6)
- # parinfer (31)
- # portkey (3)
- # programming-beginners (16)
- # re-frame (20)
- # reagent (69)
- # remote-jobs (4)
- # ring-swagger (25)
- # schema (1)
- # shadow-cljs (151)
- # spacemacs (2)
- # sql (14)
- # tools-deps (16)
- # uncomplicate (5)
- # unrepl (35)
- # vim (1)
- # yada (72)
And for those that don’t know - Chas transferred to us https://github.com/clojure-emacs/piggieback One small step towards better ClojureScript support in CIDER.
I’ll speak with him soon to get some access to nREPL as well so we can help with the 0.3 release and whatever lies next.
It’d be really cool of we implement this https://github.com/clojure-emacs/piggieback/issues/73 That would large eliminate the need for two REPLs per project, as you’d be able to toggle between clojure/clojurescript with just one REPL.
This is awesome
with latest clojure-mode
from MELPA, is this happening only for me: https://github.com/clojure-emacs/clojure-mode/issues/474 ?
Anyone know if there is progress on the "sesman" issue for Cider? I'm still stuck on Cider 14 waiting for the regression to be fixed.
@manuel it’s a regression from the massive font-lock refactoring that was recently merged. I had a feeling this was not going to happen. 🙂
@magnars No progress yet. Not sure when @vspinu is going to have time for this. Btw, did you have a problem with cljs/clj switching or what? At least this part we already fixed.
What pains me is that most such problems are not hard to fix, but I sadly have no time to address them.
Yes, I had issues switching between clj and cljs in the same project, as well as clj-repls in different projects at the same time.
This is fixed, the other is not fixed, but it should be that hard to fix even without sesman. It’s a big gun. 🙂
I often regret adding this dynamic repl switching. Life was so easy with only static dispatch. 🙂
I imagine your life is never easy with all of us complaining all the time and rarely being thankful
I just wish this was my full time job and I had the time to address all of your complaints.
> I just wish this was my full time job Really? Then who’ll manage Rubocop? Or Prelude? Or… :thinking_face:
@bozhidar: release CiderCoin. Each holder of CiderCoin is given a lifetime, non-transferrable, royalty free access to https://github.com/clojure-emacs/cider
Yes, Cider would be a great project for Clojurists Together
@danielcompton I’m shilling for you
It would be great to get an application from @bozhidar or another CIDER maintainer if any of you have time
Sure, but hopefully the idea is that the 💰 can buy some 🕰️
Obviously that doesn't work for everyone though
@arrdem: How would CiderCoin be a Ponzi scheme? It's only promise is that each holder is entitled to a lifetime, non-transferable, royalty free access to https://github.com/clojure-emacs/cider Unlike 99% of other coins out there, CiderCoin would deliver on it's promise, and unlike 99.999% of other coins out there, CiderCoin would deliver it's promise before ICO 🙂