This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aleph (10)
- # announcements (4)
- # beginners (25)
- # calva (4)
- # cider (78)
- # clj-kondo (10)
- # cljdoc (1)
- # cljs-dev (58)
- # clojure (51)
- # clojure-austin (5)
- # clojure-dev (90)
- # clojure-europe (2)
- # clojure-greece (2)
- # clojure-italy (3)
- # clojure-nl (63)
- # clojure-quebec (1)
- # clojure-seattle (2)
- # clojure-spain (4)
- # clojure-spec (19)
- # clojure-uk (25)
- # clojuredesign-podcast (5)
- # clojurescript (24)
- # crux (1)
- # cursive (15)
- # datomic (1)
- # events (1)
- # figwheel-main (10)
- # fulcro (62)
- # graphql (7)
- # keechma (11)
- # nrepl (1)
- # off-topic (12)
- # re-frame (8)
- # reitit (2)
- # remote-jobs (3)
- # shadow-cljs (127)
- # specter (1)
- # sql (43)
- # testing (2)
- # tools-deps (30)
Seems after upgrading I'm no longer to evaluate anything, instead I get exceptions in the
No such var: info/resource-path
(a small mismatch between cider-nrepl and orchard that resulted in that missing
You can just delete your current installation and pin the cider package to
using emacs I tend to start a nrepl with lein nrepl and then cider-connect to connect to it... I get the warning 'WARNING: CIDER requires cider-nrepl to be fully functional. Many things will not work without it!'...
tbh I'm confused now of what I need to do with a plugin and what with deps in package.clj to get cider working.
@macrobartfast I used to get this message when the version of cider-nrepl was different (or not included) in my
.lein/profiles.clj configuration. Quick check would be to quit the
lein repl repl and use
cider-jack-in from Emacs instead (moving any
.lein/profile.clj file out of the way first), as this will inject the right version of libraries for the CIDER version you have installed. Then just look in the messages buffer to see what to use.
[nREPL] Starting server via /home/jr0cket/bin/lein update-in :dependencies conj \[nrepl\ \"0.6.0\"\] -- update-in :plugins conj \[refactor-nrepl\ \"2.5.0-SNAPSHOT\"\] -- update-in :plugins conj \[cider/cider-nrepl\ \"0.22.0-beta6\"\] -- repl :headless :host localhost... [
I do not use a
.lein/profiles.clj it is not needed if you are using
cider-jack-in, unless you are on a really old version of CIDER, circa February 2015. Move your profiles.clj out of the way first
Its okay to use a terminal to start the REPL using
lein repl but you need to manage the versions of the plugins for the version of cider you have installed. So whenever you upgrade CIDER then you may need to update your
.lein/profile.clj. CIDER has taken on some pretty big improvements and consolidated lots of code from other libraries, so its simpler to use
cider-jack-in and let CIDER do the work for you 🙂
There are some excellent docs on different ways to run/connect to the REPL if
cider-jack-in doesnt meet your needs https://docs.cider.mx/cider/basics/up_and_running.html.
maybe for #clojure, but what is a good way to jump to a function declaration and pop back?
I'm finding cider-find-var requires everything have been already loaded somehow, which is awkward.
@macrobartfast you are not the first to mention this limitation of cider-find-var. I always have the REPL running so don't notice the issue much. I use a lot of the tools in Spacemacs to navigate around.
(use-package lsp-mode :init (setq lsp-clojure-server-command '("bash" "-c" "cd ~/projects/clojure/clojure-lsp && lein run")) (setq lsp-enable-indentation nil) (setq lsp-enable-completion-at-point nil) ;; (setq indent-region-function #'clojure-indent-function) (add-hook 'clojure-mode-hook #'lsp) (add-hook 'clojurec-mode-hook #'lsp) (add-hook 'clojurescript-mode-hook #'lsp) :config (require 'lsp-clojure))
could a couple unix guys test this : https://github.com/clojure-emacs/cider/pull/2657 ?
if I'm using double quotes and the value in between double quotes includes
$(something) then that will be evaluated by the shell
the situation is that right now, cider won't jack(in a deps.edn project on windows without the changes i proposed, and i'm not knowledgable enough to handle the unix side of things, just good enough to test it
generally you assume the worst when shelling out, because you don't know how that arg or other args will be used in the future
I'm not knowledgeable enough about windows to be of help on that side, I'm just saying this is a bad idea
sounds like there should be a switch or something to let it work differently based on platform, then
like a function to quote an argument and have it automatically wrap it in the correct quotes for the platform and to escape any quotes or whatever within the arg
that should just be a normal emacs buffer/frame configuration thing? Do you mean just constraining the size of the repl that opens up?
one thing i dislike is when you drill down, say from test result to exception window then to code, i end up with code in my repl window, and sizes don't go back to what they were
It's not a cider specific thing. It's one of the most annoying aspects of Emacs in general.