This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # adventofcode (129)
- # architecture (10)
- # beginners (163)
- # boot (1)
- # cider (34)
- # cljs-dev (9)
- # clojure (210)
- # clojure-austin (11)
- # clojure-czech (2)
- # clojure-gamedev (1)
- # clojure-greece (67)
- # clojure-italy (2)
- # clojure-russia (8)
- # clojure-spec (36)
- # clojure-uk (54)
- # clojurescript (87)
- # cursive (12)
- # data-science (6)
- # datomic (13)
- # devcards (4)
- # editors (2)
- # emacs (34)
- # figwheel (6)
- # fulcro (147)
- # graphql (17)
- # lumo (54)
- # off-topic (37)
- # om (11)
- # onyx (7)
- # parinfer (10)
- # random (1)
- # re-frame (13)
- # ring (10)
- # ring-swagger (2)
- # sfcljs (1)
- # shadow-cljs (1)
- # spacemacs (32)
- # test-check (4)
- # unrepl (84)
I'm beginning to think I have a lower tolerance than many when it comes to infelicities in tooling. I'm definitely frustrated by the balkanization we currently have. Not enough stuff is written to be easily applied in different environments. That's one of the reasons I'm kinda interested in getting Cider to support the socket repl.
I just haven't yet learned enough to be able to fix all of the things I'm frustrated with 🙂 All of those who work on tooling are obviously looking to improve things, and have the skills to actually do so.
@grzm communicating is hard. Isolated experiments allow rapid growth within that glass house. I'm also very keen to see an improvement to tooling! I have a low tolerance for broken things, and the pedant in me loves fixing those things. We should definitely collaborate on pushing forward CIDER :)
I'll probably continue tinkering. There are only so many round tuits. Gotta figure out where to use mine, or get more.
I don’t always have time for doing the coding myself, but I usually find time to help people with PRs and ideas.
> I’m beginning to think I have a lower tolerance than many when it comes to infelicities in tooling. I’m definitely frustrated by the balkanization we currently have. Not enough stuff is written to be easily applied in different environments. That’s one of the reasons I’m kinda interested in getting Cider to support the socket repl.
I completely agree with this sentiment! And funny enough, I leave in the very heart of the Balkans! 😄
@bozhidar As long as we have you here, can I bug you to share some insight on CIDER innards that are causing me trouble? The output of
(cider-scale-background-color) returns color codes like "#22e322e322e3". Is this expected? (I'm on 0.15-London)
there are imbalanced parens in CIDER right now. it does not successfully read at the moment
@daveliepmann What’s wrong with this? Is it not a valid color code? (I don’t remember color codes of the top of my head 🙂 )
12-digit color codes exist. I'm just not sure that they work in emacs, or whether they're meant to be output from
cider-scale-background-color. I know that 12-digit colors (from that fn) break
cider-stacktrace-frames-background-color on my system (`version` GNU Emacs 25.3.1 (x86_64-apple-darwin17.2.0, Carbon Version 158 AppKit 1561.1) of 2017-11-27;
cider-version CIDER 0.15.1 (London)).
Specific breakage described in this issue: https://github.com/jackrusher/dotemacs/issues/33 (which is also the repo with my theme "eigengrau", but I am 99% sure my theme has nothing to do with it.)
Correction: I think the bug is in
cider-scale-color, not scale-background-color.
i'm ont sure but i'm thinking it's the new when-let* and autoloads not playing nice together. but i don't have any reason why tat would be the case
Hi folks. Got a question. I’ve got a case that a function which when I’m evaling it, gives me
java.lang.Long cannot be cast to clojure.lang.IFn, but if I’ll step through and debug, it finishes successfully. Would you have any tips how I can trace finding what’s the problem here?
It’s a bit nasty as I’ve been playing with advent of code, give me a sec, I’ll create a gist with it.
https://gist.github.com/zeroDivisible/bf75d84b8ad73e00215e3a2ade4a11ab - the one at the very bottom is the invocation which fails for me when running, but works when debugging. Not sure if worth mentioning but I’m playing with latest Spacemacs, Cider & Clojure 1.9