This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-05
Channels
- # 100-days-of-code (1)
- # announcements (9)
- # aws (1)
- # beginners (195)
- # braveandtrue (60)
- # calva (3)
- # cider (36)
- # cljs-dev (3)
- # clojure (124)
- # clojure-canada (13)
- # clojure-dev (18)
- # clojure-germany (2)
- # clojure-italy (2)
- # clojure-losangeles (1)
- # clojure-nl (9)
- # clojure-russia (1)
- # clojure-spec (20)
- # clojure-uk (109)
- # clojurescript (49)
- # core-logic (29)
- # cursive (7)
- # datomic (62)
- # defnpodcast (1)
- # devcards (11)
- # docker (3)
- # duct (6)
- # figwheel (13)
- # figwheel-main (57)
- # fulcro (2)
- # graphql (11)
- # hyperfiddle (3)
- # jobs (5)
- # jobs-discuss (9)
- # leiningen (2)
- # lumo (1)
- # off-topic (12)
- # onyx (2)
- # pedestal (1)
- # portkey (2)
- # rdf (1)
- # re-frame (39)
- # reitit (13)
- # remote-jobs (2)
- # rum (5)
- # shadow-cljs (82)
- # tools-deps (48)
- # unrepl (3)
- # vim (12)
- # yada (1)
i just found out that i had delete-by-moving-to-trash
enabled! the invalid cider-repl-history
file is still there so i'll create a github issue for the problem from yesterday 🙂
Hi folks, in one project, when i do cider-jack-in-clj&cljs
, my cljs repl buffer will have type [clj] rather than [cljs]
I see some deps are a bit old, reagent for example. would it make sense to upgrade these?
so if I kill a buffer by accident, is there a way to tell sesman
to create a new one? I keep getting SElecting killed buffer
on every new cider-connect-cljs
Yeah, seems like a bug we overlooked. Will fix it soon. I think 2-3 people reported this already.
ok cool thank you
Has anyone seen the following error: error in process filter: queue-enqueue: Wrong type argument: queue, #s(queue nil nil)
?
It comes from nrepl-client.el
and it seems to be somehow related to order of loading code, because when I evaluate nrepl-client.el
contents manually it goes away.
i've seen something like this when bytecode representation of elisp records changes across emacs versions
@dottedmag You made my day! PR welcome!
I can’t even remember what tool I used to draw this basic chart a while ago, but I’d love to have this version in the manual. 😄
@bozhidar Manual still talks about cider-toggle-connection-buffer
though it has been removed.
Unfortunately I didn’t have time to review it completely before the releases. I’m certainly that’s not the only outdated info there. PRs welcome!
I'll file a ticket for now, as I have no clue what to write instead of the obsolete text (if I knew I wouldn't be reading it in first place :)
I’m trying to turn of the checks cider dependency checks, specifically this one: https://github.com/clojure-emacs/cider/blob/7f1c5e2ea9b5271c9c7fd43b44b6f4a1a1262183/cider.el#L650-L653
I would have guessed cider-check-cljs-repl-requirements
is the flag to set, but it seems to be not used. Am I overlooking something?
@kommen it looks like there is a bug and it is not possible right now. This can be suppressed with the optional no-error
passed to cider--check-cljs
but this parameter is not passed from cider--update-cljs-init-function
if you are doing cider-jack-in-clj&cljs
you can do it by passing a second argument no-error
. I'm not sure how to do that interactively. Not sure how interactive functions work with two optional parameters