This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-09
Channels
- # announcements (1)
- # architecture (20)
- # aws (22)
- # babashka (41)
- # beginners (191)
- # chlorine-clover (66)
- # cider (19)
- # clj-kondo (54)
- # cljs-dev (15)
- # cljsrn (78)
- # clojars (1)
- # clojure (148)
- # clojure-android (4)
- # clojure-europe (7)
- # clojure-gamedev (15)
- # clojure-germany (6)
- # clojure-losangeles (46)
- # clojure-nl (23)
- # clojure-survey (3)
- # clojure-uk (46)
- # clojurescript (24)
- # conjure (21)
- # cursive (21)
- # data-science (11)
- # datomic (5)
- # events (2)
- # fulcro (28)
- # garden (32)
- # joker (2)
- # kaocha (6)
- # lambdaisland (4)
- # mount (2)
- # off-topic (11)
- # pathom (10)
- # pedestal (13)
- # re-frame (7)
- # shadow-cljs (15)
- # spacemacs (21)
- # specmonstah (1)
- # wasm (1)
- # windows (1)
- # xtdb (37)
;; TODO Split up into multiple modules.
;; TODO Refreshing of namespaces.
;; TODO Test running.
;; TODO Handle stdin requests.
As well as eval form at mark and completion to go. Then documentation time!
❤️ 8
Of course, it's a good feature! I want to see if I can improve it now that all my code is inside nvim's process too.
Since all of the code is inside nvim's process now the eval at mark code correctly blocks the UI. No more flicker to another buffer! It just magically evals the right thing!
👏 4
So I can be in a Clojure buffer, hit ,emP
and it'll eval the code at P
even though it's in a Fennel buffer.
Not that you'll be working across multiple lisp types very much but it's good for internal dev.