This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aws (3)
- # beginners (61)
- # boot (1)
- # cider (80)
- # clara (5)
- # cljs-dev (5)
- # cljsrn (19)
- # clojure (40)
- # clojure-dev (29)
- # clojure-dusseldorf (2)
- # clojure-greece (21)
- # clojure-italy (16)
- # clojure-russia (7)
- # clojure-spec (31)
- # clojure-uk (70)
- # clojurescript (31)
- # cursive (21)
- # data-science (5)
- # emacs (7)
- # fulcro (23)
- # graphql (4)
- # java (18)
- # jobs (1)
- # jobs-discuss (25)
- # juxt (14)
- # nrepl (2)
- # off-topic (18)
- # om-next (2)
- # onyx (3)
- # re-frame (16)
- # reagent (50)
- # ring-swagger (5)
- # shadow-cljs (70)
- # specter (5)
- # sql (24)
- # tools-deps (16)
- # vim (41)
I'll not talking about graal, just the default cider format command, which uses cljfmt code. I'm wondering if people use it. https://github.com/clojure-emacs/cider-nrepl/blob/master/src/cider/nrepl/middleware/format.clj
anyone else getting issues trying to install cider
Error (use-package): Failed to install cider: Failed to verify signature: "spinner-1.7.3.el.sig" Error (use-package): Cannot load cider
I am using use-package as such
(use-package clojure-mode :ensure t) (use-package cider :ensure t)
is there a way to require cider but have it point to a local spinner.el file for the dependency?
@bozhidar any idea what might be going on here? https://github.com/thheller/shadow-cljs/issues/273#issuecomment-387696388
No idea. I can’t imagine how this can be connected somehow to CIDER, but I guess it is. It’s just that the error is quite generic and gives me no clue as to what’s the real problem.
I'm questioning the use of creating a sibling repl without the primary. I wonder if there are some important steps left out
I'm totally clueless .. don't even know where to look. it doesn't make any sense to me 😛
> I’m questioning the use of creating a sibling repl without the primary. I wonder if there are some important steps left out
Well, the sibling repl is just a regular repl which you convert to cljs. There’s nothing special about it. I’m actually planning to make it possible to jack-in just to a cljs REPL.
its after a cider connect i guess. still feels a bit weird. but i thought that was out track state message but its a shadow-cljs message. I'm trying to track down where that chan is read in shadow
the message appears in the log and happens in another thread not the REPL thread. thats the part I don't understand.
in shadow-cljs there is a "worker" thread when you start a
watch for the build. that worker does the recompile. in this case the recompile fails and when trying to get more info for the warning it fails with this weird error
Hmm… after installing CIDER 0.17, trying to jack in fails with: `Error loading refactor-nrepl.middleware: java.io.FileNotFoundException: Could not locate cider/nrepl/middleware/util/misc__init.class or cider/nrepl/middleware/util/misc.clj on classpath., compiling:(refactor_nrepl/middleware.clj:1:1) Exception in thread “main” java.lang.RuntimeException: Unable to resolve var: refactor-nrepl.middleware/wrap-refactor in this context, compiling:(/private/var/folders/fg/1tzg0xt88v5bp20059blypr00000gq/T/form-init7039836408815040552.clj:1:9942)`
@deep-symmetry same for me. Will try to look into it later tonight, but maybe you’ll find a solution before I do :-)
it's got a refactor nrepl message in there. try without that to see if you can get CIDER up and running without it?
CIDER injects the version of refactor-nrepl it needs, so if it is getting the wrong one, that’s a bug in CIDER itself.
For now, I have checked out CIDER 0.16.0 from GitHub, and have tricked Emacs into installing the package from the git repo, and things seem to be working albeit without the snazzy new 0.17 features.
M-x only shows functions you can invoke easily by the modeline or with your curson in a buffer. more complex things are best left as code (non-interactive)
@dpsutton do you know if cider/piggieback is getting included and inserted into the middleware when starting
cider-jack-in-clojurescript when using Clojure CLI tools
no i don't know how the merging up the edn files works. i think @dominicm knows the most about it but i can root around for a second
you can see how its done for jacking in with clj at
cider-jack-in-params and then emulate that. but i don't think there's one for cljs
(defun cider-jack-in-params (project-type) "Determine the commands params for `cider-jack-in' for the PROJECT-TYPE." (pcase project-type ("lein" cider-lein-parameters) ("boot" cider-boot-parameters) ("clojure-cli" (format cider-clojure-cli-parameters (concat "[" (mapconcat (apply-partially #'format "\"%s\"") (cider-jack-in-normalized-nrepl-middlewares) ", ") "]"))) ("shadow-cljs" cider-shadow-cljs-parameters) ("gradle" cider-gradle-parameters) (_ (user-error "Unsupported project type `%s'" project-type))))
i think you'll need to make a custom one at this point so that stuff is there at the beginning and then a custom cljs jack in type to then invoke it?
and it looks like there's no utility function to do that so you'll need to do an add-to-list on that list
which I'm sure shouldn't be needed as
clojure-cli should ensure that
piggiback is included
@deep-symmetry clj-refactor decides what to inject for itself it only uses cider machinery for the injection
@benedek @deep-symmetry that worked for me. I only use packages from “melpa-stable”. So, I uninstalled the stable version of clj-refactor, added the ‘ordinary’ melpa package url, and installed clj-refactor v20180420. Now cider works!
Big thanks for the tips. I was digging around to find the problem, but I wasn’t even close to clj-refactor…
Yes, I also use melpa-stable and would prefer to stay that way. It sounds like the error was putting cider 0.17 on melpa-stable before its dependencies were?
A cljr release is long overdue but low prio as the latest snapshot works fine with newest cider
But this just reinforcing how painful packages are in emacs. I don’t want to have to learn all these details but I guess I’m going to have to.
The nice thing with emacs is, when things breaks you can often poke around in the elisp source and solve it yourself
Agreed, and I’ve done that and even contributed emacs packages in the past. But when I’m putting in multiple weeks of overtime working hard in a different language and environment isn’t when I want to do that! Anyway, thanks for identifying the problem, I now know what I need to do if I want to move back onto 0.17.