This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aws (3)
- # beginners (18)
- # boot (3)
- # cider (47)
- # clara (54)
- # cljs-dev (62)
- # clojure (104)
- # clojure-berlin (1)
- # clojure-denver (1)
- # clojure-italy (1)
- # clojure-nl (22)
- # clojure-russia (30)
- # clojure-spec (28)
- # clojure-uk (95)
- # clojurescript (31)
- # cloverage (1)
- # cursive (1)
- # datomic (17)
- # duct (4)
- # emacs (27)
- # fulcro (36)
- # graphql (1)
- # hoplon (1)
- # jobs-discuss (1)
- # lein-figwheel (1)
- # lumo (2)
- # off-topic (44)
- # om-next (5)
- # onyx (29)
- # precept (1)
- # re-frame (8)
- # reagent (7)
- # ring (1)
- # ring-swagger (2)
- # schema (4)
- # shadow-cljs (185)
- # spacemacs (21)
- # specter (59)
- # tools-deps (7)
- # vim (15)
- # yada (1)
Master plan: diversification, multiplication, evolution, SINGULARITY!!! (through morning greetings)
I'm less up than usual (tho north being up is obviously just a social rather than physical thing)
how thoroughly post-modern we are that concepts of both time (UTG) and space (up t/here) have become but social constructs to us @otfrom
Morning All - I realise this is a VERY LATE comment, but I recently switched to Spacemacs from Emacs + EmacsLive and I am loving it. There is a part of me that won't dare go near Cursive for fear that I might never use Emacs again...
@maleghast I'm just at the point where Emacs keybindings are in my head now.... continually hammering C-x C-s in Keynote while editing slides before work did not have the desired effect 🙂
Hehe - I know what you mean @jasonbell; whenever I use Vim now I have to really think hard about keybindings as I now use Emacs more than Vim. The one thing I really like about Atom for Python (when I need to be snakey) is that some of the really low-level key bindings (like C-e / C-a) just work so I don't have to think too hard about context switching.
I'm pretty happy with moving most of my config over to use-package https://github.com/otfrom/otfrom-org-emacs
I found spacemacs/prelude/others to difficult to add things too when I wanted to change stuff
I would be interested in test-driving your setup @otfrom - for one thing I do feel like a bit of a traitor using Spacemacs... 😉
it just wasn't right for me and I've declared emacs config bankruptcy something like 5-8 times in my 20yrs of using it
I am using it and loving it (mostly), but I would like to ascend to greater / loftier Emacs heights at some point, and in the end that means my own config, but I am a realist - I will only get to my own config by cribbing off someone else to start with, starting from scratch is just too daunting for me.
So from time to time I test-drive other people's setups to see if I like them enough as a jumping off point. EmacsLive was great to me for years, but Sam stopped updating it and I needed something that was more current...
I've heard people talking about Prelude, but not got around to seeing if I like that one...
@maleghast nope - life is too short for your own emacs config. i'm not as far gone as @otfrom, (having only had maybe 4 or 5 emacs-config bankruptcies) but i have concluded that spacemacs and prelude both offer you a sane starting point from which to customise. try them, choose one (i tried prelude first, then switched to spacemacs and stuck with it, mostly because i like helm and the windowing behaviour), but, unless you don't have anything else to do, don't start from scratch 😬
git config --global alias.recent "for-each-ref --format='%(refname:lstrip=2)' --sort=-committerdate refs/heads/ --count=5"
(What this does is,
git recent lists 5 branches with most recent commits. I tend to jump between branches a lot and forget the names. No more!)
I find this especially taxing as my branch names are taken from JIRA tickets and lack any intrinsic meaning. :face_with_rolling_eyes: I just try to tidy up the old branches as I go to keep the list manageable. Might add your suggestion to my list of aliases, @lady3janepl.
that works for tickets 🙂 I have exploratory development branches interspersed with tickets, and also do experimental rebases so keep backups…
(but we were able to temporarily escape the red tape because of a fairly separate project.)
I tried spacemacs but it wasn't as pretty as my emacs and was a bit too vimmy. If I want vim, I'll er, just use vim
for a single project I don’t see the need for anything more complicated than trello + github workflow. I imagine that when you’re higher up and need to see burndown charts, multiple teams coordinating and whatnot, you probably want something more involved.
Heavens, I loathe JIRA. The software embodiment of the toxic doctrine of Taylorism. I spit copiously upon his hateful legacy.
Frederick Winslow Taylor, the architect of scientific management. Made himself so popular that only one person attended his funeral.
I don't mind Trello - seems to do what's required. JIRA just seems like a bit of a behemoth. It seems to take over to the point where the project becomes JIRA, and its artifacts are the main focus of attention.
Oh dear - hope it isn't a Microsoft-style "Embrace, extend, extinguish" manoeuvre.
We used JIRA for a short period. It definitely has the feeling of too many bells and whistles. Results in a very clunky feel and as such didn't result in enough "buy in" from management and the dev team. Admittedly, it's a smallish start-up so ymmv. Trello is nice, as is Clubhouse. http://Waffle.io is also pretty nice for doing doing agile boards tide to github repositories
both of those look interesting, I found trello integration with github somewhat lacking
We're using Clubhouse at the moment which has more process than Trello, but being PM oriented gives it an edge in UI. But we're not fully certain of our decision yet.
we name our branches
x.y.z for version integration branches, and
x.y.z-feature for feature branches diverging from & merging to a given integration branch... then we cull old branches mercilessly, which is quite easy given the naming
Does anyone have a working example of
cloverage usage? I pass it a regex and it seems to completely ignore it…
We're using it in most of our (boot) components, except the ones using ring/compojure, as I believe it gets well confused by that
Our boot task is
but we basically just cribbed that from t'Internet somewhere, without necessarily understanding all of it 😉
(require '[cloverage.coverage :as cloverage] '[bultitude.core :as bultitude]) (deftask coverage "Run test coverage on the project."  (with-pass-thru _ (let [namespaces (map name (mapcat bultitude/namespaces-in-dir (get-env :directories))) [src-ns test-ns] ((juxt remove filter) #(.contains % "test") namespaces)] (binding [cloverage/*exit-after-test* false] (apply cloverage/-main "--summary" "--html" "--text" "--emma-xml" "--output" "coverage" (concat (mapcat #(list "-x" %) test-ns) src-ns))))))
whatever options I pass to try to restrict which tests get run, it just seems to run those tests as well as running all the tests (so some get run twice)
I’m trying to resist the urge to
rm-rf <tests I don't want run> && lein cloverage && git checkout -- <those tests again>