This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-21
Channels
- # beginners (5)
- # boot (15)
- # capetown (1)
- # chestnut (2)
- # cljs-dev (9)
- # cljsjs (3)
- # cljsrn (1)
- # clojure (190)
- # clojure-brasil (2)
- # clojure-greece (14)
- # clojure-italy (3)
- # clojure-poland (8)
- # clojure-romania (1)
- # clojure-russia (2)
- # clojure-serbia (3)
- # clojure-spec (38)
- # clojure-uk (98)
- # clojure-ukraine (2)
- # clojurescript (65)
- # clojurex (1)
- # core-async (16)
- # cursive (16)
- # datomic (3)
- # defnpodcast (7)
- # emacs (11)
- # funcool (2)
- # hoplon (16)
- # jobs (1)
- # leiningen (4)
- # lumo (9)
- # off-topic (2)
- # om (1)
- # other-languages (1)
- # protorepl (1)
- # re-frame (50)
- # reagent (16)
- # reitit (32)
- # remote-jobs (1)
- # rum (1)
- # shadow-cljs (73)
- # spacemacs (36)
- # specter (21)
- # sql (6)
- # unrepl (107)
- # untangled (4)
Still running into a fair amount of issues with my autocomplete and proto-repl -_- What’s odd is that everything works well when I disable the Ink console :thinking_face: Been spelunking the proto-repl package and seems like `window.protoRepl.parseEdn` in `completion_provider.coffee` is not returning the expected output. Which led me to the `edn_reader.js` file, but that thing is a +2000 line mammoth :astonished: Anyone know what that files is responsible for? My brief googling sessions got me as far as edn stuff is a way to format and pass along data, but I’m confused as to why this `edn_reader.js` seems so dense/convoluted?