This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-25
Channels
- # aws (2)
- # bangalore-clj (2)
- # beginners (90)
- # boot (89)
- # bristol-clojurians (1)
- # cider (23)
- # cljs-dev (48)
- # cljsjs (2)
- # cljsrn (3)
- # clojure (118)
- # clojure-argentina (3)
- # clojure-austin (8)
- # clojure-czech (1)
- # clojure-dev (18)
- # clojure-ireland (1)
- # clojure-italy (4)
- # clojure-russia (6)
- # clojure-spec (75)
- # clojure-uk (224)
- # clojurescript (103)
- # core-async (28)
- # cursive (3)
- # datascript (7)
- # datomic (15)
- # dirac (30)
- # emacs (14)
- # events (3)
- # figwheel (1)
- # hispano (1)
- # hoplon (176)
- # lambdaisland (1)
- # lein-figwheel (6)
- # off-topic (21)
- # om (7)
- # onyx (2)
- # pedestal (6)
- # re-frame (4)
- # reagent (15)
- # spacemacs (67)
- # specter (13)
- # testing (9)
- # untangled (65)
- # vim (6)
- # yada (1)
@ggaillard don't underestimate how much more productive and relieved you can get after a short holiday.
@theblackbox It’s implemented here https://github.com/ymilky/franzy/blob/master/src/franzy/clients/consumer/client.clj#L208. Actually, I remember getting a somewhat similar protocol exception when I was testing Franzy. I didn’t figure out what was causing it and ended up implementing a simple Kafka-client wrapper myself.
@richiardiandrea : I'm actually not even using inf-clojure. I'm literally using clojure-mode + inferior-lisp. 🙂
but because everything is programamble, I'm about to do something very cool. My use of eamcs has 2 monitors + 4 frames, 2 frames per screen.
I'm about to implement a key, which fires up "boot-dev" in frame3, aand "boot-repl" in frame 1
This is the type of thing that's trivial to do when building from scratch, but I have no idea where to begin with cider.
Yeah cool
@tbaldridge haha true… sorry for the late reply 🙂
@dotemacs: it's not private, it's just part of a 650 line org file (which generates my emacs.el) that's a bit embrassing to share
it's literalrly just 4 frames, named f0 f1 f2 f3; and I just send buffers to those frames
@qqq oh don’t worry about that, I always have grand plans on how to organise my initi.el and then when I’m at some 80% I give up and go into a complete mess, at which point I just give up and reduce it to the smallest subset of the required features… until I start to add more packages/tweaks … the cycle repeats
yeah, the one thing that bugs me about emacs is the way new buffers / windows / frames are created / handled
I wish there was a 'hook' function where whenever emacs wants a new buffer/window/frame, it consults me
then my hook function gets to decide where the new thing, if created at all, is placed, or if it re-uses an oldone
i'm testing out this "multi frame" appraoch since having one full screen frame + lots of widows doesn't work out as eamcs move my windows around for me at will and replaces them at will
@qqq would this help somewhat: https://www.gnu.org/software/emacs/manual/html_node/elisp/Window-Hooks.html
@qqq see this package: https://github.com/emacsorphanage/dedicated/blob/master/dedicated.el
cheers @konukhov still in the very early stages of Clojure dev so I was working my way through the example by refactoring to try to make sense of the components. During the refactor I think I missed some parens so the "object" I was passing to said function was actually a reference to the function that creates my consumer and not the Kafka Consumer that was expected. So I'm guessing that the protocol method was implemented but not for the data structures I was passing it, hence the error. Still learning but it's starting to make sense.