This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-12
Channels
- # bangalore-clj (4)
- # beginners (77)
- # boot (71)
- # cider (10)
- # clara (1)
- # cljs-dev (52)
- # cljsjs (28)
- # cljsrn (1)
- # clojure (390)
- # clojure-dev (5)
- # clojure-india (1)
- # clojure-italy (5)
- # clojure-nl (24)
- # clojure-poland (4)
- # clojure-russia (123)
- # clojure-spec (71)
- # clojure-taiwan (2)
- # clojure-uk (8)
- # clojurescript (236)
- # core-matrix (6)
- # cursive (19)
- # datomic (16)
- # defnpodcast (2)
- # editors (1)
- # emacs (36)
- # garden (2)
- # hoplon (5)
- # jobs (1)
- # jobs-discuss (10)
- # juxt (47)
- # luminus (4)
- # lumo (6)
- # off-topic (207)
- # om (1)
- # onyx (20)
- # pedestal (40)
- # perun (2)
- # re-frame (8)
- # reagent (48)
- # ring (2)
- # ring-swagger (2)
- # specter (13)
- # unrepl (89)
- # vim (6)
question to you arch-ers: do you use desktop/window managers (or ecosystems) and which one do you find most pleasant to work with daily?
quite nice as of my taste: performant and stable enough, though you have all the stuff like automount/network/energy saving etc. without need for installing and tuning too much by hand
@dominicm not sure I get https://github.com/juxt/mach/issues/24
@jonpither plan depends on main. main gets called twice.
funnily enough tho, in trying to reproduce, I find a related bug with the new mach/props, the props get evalled per rule invocation (which may again.... be OK
Not sure if mach should assume non-freshness in the case of it already being run in the same process.
not got brain power to figure out what mach/props are right now. but it wouldn't surpirse me.