This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-16
Channels
- # admin-announcements (2)
- # bangalore-clj (3)
- # beginners (15)
- # boot (303)
- # carry (18)
- # cider (7)
- # cljs-dev (222)
- # cljsrn (103)
- # clojure (196)
- # clojure-czech (2)
- # clojure-russia (69)
- # clojure-spec (21)
- # clojure-uk (48)
- # clojurescript (68)
- # cursive (18)
- # datomic (185)
- # events (1)
- # hoplon (2)
- # lambdaisland (1)
- # leiningen (1)
- # mount (10)
- # off-topic (1)
- # om (14)
- # onyx (154)
- # parinfer (1)
- # pedestal (3)
- # planck (5)
- # protorepl (9)
- # re-frame (17)
- # reagent (27)
- # ring (2)
- # specter (58)
- # test-check (1)
- # testing (7)
- # untangled (59)
- # yada (35)
@jgrimes: you may have already found this but the relevant code is here https://github.com/jasongilman/proto-repl/blob/master/lib/proto-repl.coffee#L535
Note that I haven't updated replumb in a while so that might be a good first step.
I've had keybinding issues since I first created Proto REPL. There seems to be no way to create a common set of keybindings that don't conflict with something. https://github.com/jasongilman/proto-repl/issues/147
coming from emacs most keybindings weren't the same anyway, so I've had to customize almost everything
The node build chain makes me sad. Got node-gyp errors, then managed to get npm itself in a state that it can't even update itself 😐
Gonna try to wipe node and start from scratch, 'cuz I really wanna keep using this toolset.
@jasongilman: don't push yourself too hard. Keybindings are a mess. There is no way to make everyone happy. I just disabled all keybindings in my atom jeje 😄 https://discuss.atom.io/t/key-binding-hell/12075
Thanks @carocad