Fork me on GitHub
#cider
<
2018-03-10
>
xiongtx03:03:56

@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

xiongtx03:03:07

Another thing we could do is use emacs 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.

gonewest81803:03:15

I have started some of this. I’m contributing to a project that has the emacs docker images. Silex/docker-emacs

gonewest81803:03:29

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

gonewest81803:03:17

I have an emacs init that does most of the rest.

gonewest81803:03:39

Well, there’s a Makefile too. We’d be “kickin’ it old-skool” in terms of tooling but it works.

xiongtx18:03:24

Wow, that's interesting--I've never seen that syntax before. TMYK.

arrdem06:03:51

@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.

gonewest81818:03:44

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.

arrdem06:03:25

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

arrdem06:03:03

Is there an obvious way to hook into CIDER's repl to add custom emacs-side handling for results?

arrdem06:03:41

I've got function(s) which produce image files, and it'd be awesome if I could render them inline in the CIDER REPL

benedek06:03:00

@dcj @bozhidar this seems to me a java9 issue rather than compatibility

benedek06:03:33

eg you can't jack in with cljr because cljr does not support java9 atm

benedek06:03:31

there is an open issue for that btw but upstream deps for add project deps block it for now.

benedek06:03:11

so it might just work with cljr too if you downgrade to java8

qqq15:03:39

(defun my-cider-eval-last ()
                       (interactive) 
                       ;; (cider-repl-clear-buffer)
                       (cider-eval-last-sexp)
                       )
I can't figure why uncommenting the cider-repl-clear-buffer results in an error.

gganley15:03:56

What error

qqq15:03:32

Wrong type argument: integer-or-marker-p, nil

gganley15:03:21

Do you have debug-on-error or whatever on?

gganley15:03:35

One sec let me snag the actual variable

gganley15:03:54

That’s in my config so that I get richer error messages

gganley15:03:03

Interupts my work from time to time but that’s ok

qqq15:03:27

Let me integrate that into my emacs.

gganley15:03:21

I do apologize for any profanities in the commit log

gganley15:03:19

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?

gganley15:03:27

@qqq did you figure it out?

qqq15:03:03

no, I'm still not getting a stack trace

qqq15:03:31

ah, I restarted emacs, getting stack traces now 🙂

gganley15:03:43

And the reason I’m asking is so I can add the solution you found to my “incase something goes wrong” file lol

qqq15:03:31

The weird thing is, I pasted those 3 lines into emacs.d/init.el

qqq15:03:47

I evaluated it multiple times, I even opened/closed my *.cljc file -- still no stack traces

qqq15:03:14

but then restarting emacs worked, no idea why

gganley15:03:18

Well they wouldnt pop stack traces in the Clojure sense, they would throw errors akin to when you run emacs --debug-init

gganley15:03:57

Try C-h v debug-on-error and what is the output

qqq15:03:14

I think I've found the line of the bug

qqq15:03:21

Need not to understand wtf cider is doing.

gganley15:03:35

What line?

gganley15:03:48

Through a GH link with the line