This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # beginners (356)
- # boot (4)
- # cider (44)
- # cljs-dev (73)
- # cljsrn (19)
- # clojars (5)
- # clojure (57)
- # clojure-brasil (2)
- # clojure-italy (1)
- # clojure-russia (9)
- # clojure-spec (9)
- # clojured (3)
- # clojurescript (15)
- # cursive (19)
- # datomic (10)
- # duct (3)
- # emacs (4)
- # events (1)
- # fulcro (5)
- # immutant (12)
- # keechma (3)
- # lein-figwheel (4)
- # lumo (2)
- # parinfer (11)
- # planck (4)
- # re-frame (3)
- # reagent (5)
- # reitit (1)
- # shadow-cljs (5)
- # spacemacs (6)
@gonewest818 Have you started work on CircleCI integration for CIDER? I started taking a crack at it, but noticed that CircleCI's config doesn't really have the concept of a build matrix, resulting in much repetition: https://github.com/CircleCI-Public/circleci-demo-workflows/blob/parallel-jobs/.circleci/config.yml
Another thing we could do is use docker images instead of relying on EVM: https://hub.docker.com/r/silex/emacs/ It'd be nice if we could eliminate use of external tools like EVM and Cask.
I have started some of this. I’m contributing to a project that has the emacs docker images. Silex/docker-emacs
There is a yaml syntax that can reduce some of the repetition. I have examples in other projects. See elisp-lint.el for example https://github.com/gonewest818/elisp-lint
Well, there’s a Makefile too. We’d be “kickin’ it old-skool” in terms of tooling but it works.
@xiongtx I was able to play some games with YAML's anchors and references at work to clamp down on CircleCI's build repetition but yeah it's not great.
Is this the same thing as what @gonewest818 suggested? https://clojurians.slack.com/archives/C0617A8PQ/p1520651849000009?thread_ts=1520650976.000066&cid=C0617A8PQ
Yes, in terms of using YAML anchors to reduce repetition. The part where he says he parameterized with environment variables goes a step beyond what I did.
Eg, use an anchor to select a bunch of tasks which are parameterized by environment variables and then set up a bunch of workflow steps which are the same tasks re-parameterized just with different env settings
Is there an obvious way to hook into CIDER's repl to add custom emacs-side handling for results?
I've got function(s) which produce image files, and it'd be awesome if I could render them inline in the CIDER REPL
there is an open issue for that btw but upstream deps for add project deps block it for now.
I can't figure why uncommenting the cider-repl-clear-buffer results in an error.
(defun my-cider-eval-last () (interactive) ;; (cider-repl-clear-buffer) (cider-eval-last-sexp) )
I’m not sure how possible this is but I’ve been thinking about “twitch plays pokémon” where the chat would choose what to do next. Could we have a
emacs.d GH repo where any submitted PR would be automatically accepted?
And the reason I’m asking is so I can add the solution you found to my “incase something goes wrong” file lol
I evaluated it multiple times, I even opened/closed my *.cljc file -- still no stack traces
Well they wouldnt pop stack traces in the Clojure sense, they would throw errors akin to when you run