This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-01
Channels
- # announcements (3)
- # beginners (59)
- # calva (23)
- # cider (58)
- # clojure (125)
- # clojure-dev (18)
- # clojure-dusseldorf (1)
- # clojure-europe (21)
- # clojure-germany (1)
- # clojure-hamburg (1)
- # clojure-italy (13)
- # clojure-nl (29)
- # clojure-poland (3)
- # clojure-spec (61)
- # clojure-uk (74)
- # clojurescript (12)
- # core-async (6)
- # cursive (4)
- # data-science (7)
- # datomic (14)
- # defnpodcast (1)
- # events (4)
- # fulcro (72)
- # juxt (36)
- # kaocha (3)
- # nginx (3)
- # off-topic (14)
- # pathom (5)
- # ring-swagger (68)
- # shadow-cljs (25)
- # spacemacs (8)
- # sql (42)
- # tools-deps (8)
- # vim (6)
Well, can I add one more plug-in? I'm porting (kinda... will write about it later) my current Atom plug-in for NeoVIM (just for fun, for now. Don't know yet if it'll be a viable option). It's yet at the very beginning, but you can find it here: https://github.com/mauricioszabo/clematis. There's also a nice gif showing what's working right now.
oh wow, this one looks cool too! I like the data exploration orientation. very interesting. it's funny, most editors have one main plugin for clojure, now vim has like 5.
No, you can't evaluate each step. It's showing the integration with UNREPL, where it'll evaluate only parts of a big list/vector/map and then you can ask for more data
That way you can evaluate infinite lists, for example (like the range
case)