This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-19
Channels
- # announcements (1)
- # beginners (115)
- # calva (7)
- # cider (8)
- # clj-kondo (3)
- # cljdoc (12)
- # clojure (50)
- # clojure-europe (4)
- # clojure-italy (5)
- # clojure-nl (6)
- # clojure-spec (70)
- # clojure-uk (88)
- # clojurescript (54)
- # core-async (16)
- # cursive (5)
- # datomic (31)
- # editors (4)
- # emacs (4)
- # fulcro (29)
- # graphql (17)
- # luminus (1)
- # lumo (2)
- # off-topic (37)
- # pathom (16)
- # random (2)
- # re-frame (5)
- # reitit (3)
- # rum (2)
- # shadow-cljs (192)
- # sql (11)
I use inf-clojure, but probably in a very very basic way. All I do is bind about 3 or 4 key combos to commands that (a) start inf-clojure and connect to a socket REPL on my local machine on a particular hard-coded TCP port that I use in my projects, (b) another key to send the expression just before the cursor to the REPL and eval it, and (c) I'm not even sure I have a (c), certainly not one I use often enough to remember.
Ah, I checked my setup and there is one more I sometimes use: (c) a binding to do inf-clojure-set-ns, so that if I am in a buffer for the non-current namespace, editing a function, and I want to redefine it with the new definition in its namespace, I do not have to type (in-ns 'whatever.name.space.cursor.is.in.now), but just the key binding that does inf-clojure-set-ns, which probably somehow parses the ns form near the beginning of the file to figure it out, and send the right (in-ns ...) command and eval it for me. Then eval the function.