This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (5)
- # architecture (8)
- # beginners (7)
- # boot (41)
- # braveandtrue (1)
- # cider (77)
- # clara (3)
- # cljs-dev (56)
- # cljsjs (7)
- # cljsrn (7)
- # clojure (44)
- # clojure-austin (3)
- # clojure-brasil (1)
- # clojure-hk (3)
- # clojure-russia (137)
- # clojure-spec (14)
- # clojure-uk (44)
- # clojurescript (33)
- # cloverage (3)
- # core-async (10)
- # css (1)
- # cursive (16)
- # datomic (116)
- # devcards (14)
- # emacs (1)
- # events (1)
- # funcool (2)
- # functionalprogramming (1)
- # hammock-driven-dev (1)
- # jobs-rus (124)
- # lein-figwheel (1)
- # leiningen (1)
- # liberator (4)
- # melbourne (3)
- # mount (73)
- # off-topic (3)
- # om (4)
- # om-next (15)
- # onyx (38)
- # other-languages (4)
- # perun (2)
- # proton (36)
- # protorepl (2)
- # random (1)
- # re-frame (56)
- # reagent (7)
- # specter (4)
- # testing (1)
- # untangled (13)
- # yada (18)
I forced cider to be installed from melpa-stable, but it's still telling me cider-nrepl's version is nil. What can I do?
@echristopherson, check out http://cider.readthedocs.io/en/latest/troubleshooting/#missing-nrepl-messages-buffer and scroll down to 'CIDER complains of the
specifically I have 20160806.2354 -- which I think is what I had in melpa-unstable too, come to think of it.
I don't understand the statement "Note, that running cider-jack-in from outside the scope of a project will result in the older (0.2.6) nREPL dependency being used (at least on Leiningen 2.5.1). This is likely a Leiningen bug."
-- I infer from it that the 'scope of a project' (does that mean the CWD Emacs is running in? Or the CWD as set from within Emacs by M-x cd?) determines specifics of CIDER/nrepl...
but if I put 0.2.12 in ~/.lein/profiles.clj, shouldn't it always use that unless told otherwise?
cider-jack-in, based on what I understand, does some kind of dependency injection which is why I suppose it defaults to 0.2.6 if it can’t infer from the project what it should be using.
so you also don't know how it determines the "scope of a project" with c-j-i?
@echristopherson: You need to uninstall the previously installed version for your “pinned repository” setting to take effect.
I presume that cider just walks upward through the directory tree until it finds a project.clj (in which case it’s in a project) or not.
This is my package management code: https://github.com/raxod502/dotfiles/blob/master/init.el#L144
Yeah, I just checked. If I select a file outside a project, even if I started Emacs inside a project, I get the “vanilla” REPL not linked to a project.
(Personally, I prefer to have my packages load automatically on startup, so whenever I have a problem with them I just wipe
~/.emacs.d/elpa and relaunch Emacs.)
I have other cider pkgs available but not installed. But I do have clojure-mode and clojure-mode-extra-font-locking
In the case of using a prebuilt Emacs setup there could be any number of reasons setting the pinned repository doesn’t take effect. But you should be able to uninstall
M-x package-list-packages, then go to the stable version (find something like
Other versions: 0.13.0) and install that.
Is there a good way to just record in version control the actual versions of packages, so at any moment you can roll back to those versions (without storing the actual packages in the version control)?
I don’t think so. AFAIK there’s no way (yet) to download an old version of a package using
The only thing you can do is add them as submodules, which gives you some separation and additional convenience, at least.
In list-packages it says one package can be upgraded. How do I see which one?
I wrestled with submodules in my Vim setup... I was always tearing my hair out.
Where does Emacs get the information it needs to present the statement
Available as a package in in the window that pops up when you hit
? on a package line?
I'm not understanding why it lists unstable melpa there but not stable (I have it installed from stable now)
oh, I'm guessing now that's actually part of the actual package description/metadata
argh, I'm still getting the complaint.
WARNING: CIDER's version (0.13.0) does not match cider-nrepl's version (nil). Things will break!
I also cloned cider-nrepl, as advised in http://cider.readthedocs.io/en/latest/installation/#ciders-nrepl-middleware
but does it need to be cloned inside a project? I just put it in a toplevel directory and ran lein install within in, which seems to have put it in my local dependency repo
ok, working now from the new project (after adding the plugin to project.clj)
You can I-search (`C-s`) in the package listing, to find something like
available for upgrade.
You need to check the whole flyingmachine Emacs setup to make sure
melpa (non-stable) is not added anywhere. Presumably it is, because otherwise you shouldn’t be seeing packages from it.
I turned off
cider-inject-dependencies-at-jack-in, though, and put
cider-nrepl in my
it turns out... and here's the stupid part... I had left a really old cider-nrepl plugin vector in ~/.lein/profiles.clj
No, I was listing it since it was one thing to pay attention to according to the page linked by @akiva