This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-23
Channels
- # arachne (3)
- # aws (1)
- # bangalore-clj (2)
- # beginners (19)
- # boot (151)
- # cider (72)
- # cljs-dev (9)
- # cljsjs (7)
- # cljsrn (37)
- # clojure (215)
- # clojure-austin (1)
- # clojure-denmark (2)
- # clojure-dev (68)
- # clojure-india (1)
- # clojure-ireland (2)
- # clojure-italy (4)
- # clojure-mke (1)
- # clojure-nl (4)
- # clojure-russia (4)
- # clojure-serbia (1)
- # clojure-spec (29)
- # clojure-uk (23)
- # clojurescript (23)
- # cursive (24)
- # datomic (71)
- # emacs (5)
- # events (1)
- # gsoc (11)
- # hoplon (20)
- # klipse (4)
- # lambdaisland (2)
- # leiningen (3)
- # luminus (3)
- # off-topic (30)
- # om (40)
- # om-next (1)
- # onyx (15)
- # pedestal (19)
- # perun (7)
- # planck (23)
- # proton (1)
- # protorepl (2)
- # re-frame (35)
- # reagent (21)
- # ring-swagger (38)
- # rum (19)
- # spacemacs (9)
- # untangled (11)
- # vim (5)
- # yada (4)
i get that its to make sure the backend can handle it, but don't they go in lockstep
and this comes up because it's not connection aware. Ie, clj repl supports it but the connection you are running against doesn't
cider-find-var returns that the symbol is not resolved for all symbols. Is this the best way to move around? If so, is there some config I’m missing?
@stuartrexking are you trying to navigate around code?
Let me try that.
@dpsutton Thank you.
Me to!
@dpsutton some people might use an incompatible cider-nrepl
version or might not be using cider-nrepl
at all (the most basic cider functionality still works without it). cider-ensure-op-supported
exists mostly to prevent some ugly and confusing errors. It's not like people won't get some warnings when they start CIDER but I've noticed many people simply ignore them. Perhaps we can drop this or come up with some simpler scheme to verify compatibility.
I remembered one more thing - you can actually enable/disable certain middleware on demand (depending on the way you're using cider-nrepl
). Probably this was the main reason for adding cider-ensure-op-supported
.
Is it safe to assume that if a feature works on any connection it works on every connection?
e.g. one might be enabling all the middleware, one might not be, one might be using an outdated snapshot and so on
an interesting related ticket https://github.com/clojure-emacs/cider/issues/1161
the above looks trivial to achieve, all the pieces are there for it to be configurable, probably only an explicit cider-nrepl-version
which needs to be passed in 3 places (the places where the dependencies are calculated for the 3 build tools) is necessary...no promises of course but I'm already kind of looking at that part
@richiardiandrea Great! 🙂
@bozhidar should we disable the version check if we see that cider-nrepl-version
is set?
I will actually wait for my other PR to be in so that I won't need to rebase 😓
@richiardiandrea You've made a small mistake in your commit message - change it and I'll merge the PR right away.
just a sec
@bozhidar done and also sent a README PR on cider-nrepl
😄
I was kind of ashamed of not having a commit in cider
while being such an avid fan 😄
also probably we should suppress the wiki and/or point to the doc
only, people might think "oh the wiki is empty, there is no doc in this project" 😄
Is there support boot for the cljs repl in cider
? It looks like there is only cider-cljs-lein-repl
.
yeah, let me try if it actually works in boot
yep it looks like it is called for boot
as well
yeah that code pathway is just registered in the main cider-jack-in process. it doesn't have access to the project type and other things
but its registered as a callback and applied to the connection buffer (i think) and it was going to be a lot of work to make a closure or something
got it, at least we can change the name
but it will be breaking 😄
I'll attempt a cider-cljs-repl-form
also for boot probably piggieback
and weasel
could be auto-injected
I think this is just an oversight because originally this functionality relied on lein
- probably we need to add a similar defcustom for boot
, otherwise everyone will have to use dir-locals when switching between project types
mmm true about the first
my talk with @dpsutton about the tooling session
reminded me that it might be a good to have some glossary
section in the manual explaining some potentially confusing terms
today is my personal cider day 🙂
some (small) doc PR opened
but now it is time to rest 😉
okay I am banging my head against the wall trying to figure this out, and C-c C-o
doesn’t seem to be it (?) : how do I clear the repl buffer??
I somehow lost my muscle memory this past weekend from using intero-mode
, which uses a different key combo for this
I’m having trouble finding whatever it was I was using in the cider docs
I guess I’m looking for whatever cider-repl-clear-buffer
is set to by default?
NEVERMIND sorry for the noise
Just for the sake of completeness - it's C-u C-c C-o
(or you can simply use the menu bar entry for this command)
bozhidar yeah sorry, that’s what I came up with—basically I missed the part about the prefix (`C-u`)
which is in the docs, to be clear, I just didn’t get it