This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-25
Channels
- # admin-announcements (3)
- # alda (2)
- # beginners (10)
- # boot (44)
- # cider (31)
- # cljs-dev (5)
- # cljsjs (2)
- # cljsrn (17)
- # clojure (181)
- # clojure-austin (2)
- # clojure-brasil (18)
- # clojure-canada (1)
- # clojure-conj (5)
- # clojure-dev (11)
- # clojure-gamedev (30)
- # clojure-russia (380)
- # clojure-spec (50)
- # clojure-uk (35)
- # clojurescript (146)
- # clojutre (1)
- # component (1)
- # cursive (62)
- # datomic (27)
- # dirac (7)
- # editors (23)
- # emacs (7)
- # events (34)
- # funcool (22)
- # hoplon (134)
- # jobs (22)
- # jobs-rus (7)
- # juxt (1)
- # kekkonen (1)
- # lein-figwheel (54)
- # leiningen (7)
- # luminus (2)
- # off-topic (5)
- # om (4)
- # onyx (27)
- # proton (5)
- # protorepl (2)
- # re-frame (16)
- # reagent (29)
- # rethinkdb (2)
- # schema (1)
- # untangled (61)
- # yada (9)
How do I [or can I] include a custom layer in Proton? I’ve currently got one running under a local fork of the proton repo, but proving slightly painful to test, & ideally I’d want it separated. Sorry if I’m missing something completely obvious here...
@dancouper: that is sadly not possible. Clojurescript hast to get compiled to javascript so the only way of adding a real custom layer is compiling it
currently .proton is very powerful and can do most stuff a layer can do. If you are missing something let me know and we can try to add that
(one idea would be to read ~/.proton/ and include all files from there. So functionality can get separated
Yeah, I thought that might be the case 🙂. It was really just to have something that matches the configurations I have at my work that could be given it’s own repo to be used by a few developers; not really a problem, would have just been a nice-to-have.
The idea about reading the proton dotfile might be good - the thing I found most painful when working with layers was the fact I was working on the entire structure of proton, rather than a discrete part of it - if there was a way of separating the layers out it might make it easier to fix issues, I’m not sure how much it adds to the complexity though.
A :lang/elm
layer would be nice though. Was starting to put together the foundations for one, though the packages have some slightly convoluted dependencies with their own options. Also, heh, org-mode
Hugely impressed with Proton though, completely sold on it, thank you for this