This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-10
Channels
- # beginners (50)
- # cider (112)
- # cljs-dev (7)
- # clojure (34)
- # clojure-brasil (1)
- # clojure-greece (4)
- # clojure-italy (8)
- # clojure-nl (14)
- # clojure-russia (4)
- # clojure-uk (94)
- # clojurescript (96)
- # clojutre (5)
- # cloverage (1)
- # cursive (5)
- # datomic (59)
- # docs (53)
- # figwheel (4)
- # fulcro (1)
- # hoplon (1)
- # hyperfiddle (3)
- # jobs (3)
- # luminus (6)
- # nyc (3)
- # off-topic (9)
- # onyx (3)
- # overtone (4)
- # re-frame (2)
- # reagent (16)
- # reitit (9)
- # ring (2)
- # ring-swagger (1)
- # rum (1)
- # shadow-cljs (81)
- # spacemacs (14)
- # specter (12)
- # sql (1)
- # tools-deps (2)
- # vim (110)
for example:
(setq cider-lein-command "lein")
(setq cider-lein-parameters "with-profile +power repl")
@chris.blom I think @bhauman is asking about the cli tools, clojure
and clj
.
@chrisblom even, duplicate usernames suck
Just updated to a clean prelude install on emacs 26.1.1. My main project seems fine, but when I open the following file I get an error.
(ns file-watcher.core)
(defonce fs (js/require "fs"))
(defonce watchers (atom []))
(def cwd js/process.cwd)
(js/procs.on "exit" #(run! (fn [w] (.close w)) @watchers))
(defn watch-dir [dir callback]
(swap! watchers conj (.watch fs dir (or callback #(apply println %&)))))
The error:
undo-tree-load-history: Wrong type argument: undo-tree, [cl-struct-undo-tree [nil ([nil ([nil ([nil ([nil ... ... nil ... 0 nil]) ((#("
" 0 1 ...) . -279) (undo-tree-id1 . -1) (undo-tree-id2 . 1) (undo-tree-id3 . -1) (undo-tree-id4 . -1) (undo-tree-id5 . -1) (279 . 280) (t 23364 19015 0 0)) nil (23364 19462 848450 0) 0 nil]) ((nil rear-nonsticky nil 21 . 22) (nil help-echo cider--help-echo 5 . 22) (nil fontified nil 5 . 22) (5 . 22)) nil (23364 19015 116513 0) 0 nil]) ((#("file-watcher.core" 0 17 (face font-lock-type-face cider-block-dynamic-font-lock t cider-locals nil help-echo cider--help-echo fontified t)) . 5) (undo-tree-id0 . 17) (t 23362 61960 0 0)) nil (23364 19015 116542 0) 0 nil]) nil nil (23364 19015 116545 0) 0 nil] [nil nil ((#("b" 0 1 (cider-locals nil fontified t help-echo cider--help-echo)) . -279) (undo-tree-id6 . -1) (undo-tree-id7 . -1)) nil (23364 23080 795926 0) 0 nil] 179 5 nil]
I don't even have a repl open.
Any idea what this means?@vinai can you tell me how and what you upgraded? I've seen these types of errors before when upgrading emacs versions. I think its a change in the structs. if you can blow away the elc files it normally resolves itself
I removed ~/.emacs.d
, ran brew upgrade emacs
, then ran the prelude installer (piping it into sh)
oh right of course you are. i think osx ships with a really old emacs. i wonder if that emacs is being used to byte compile rather than the new one installed with brew
and its totally possible that this is all on the wrong track. but this should tell us
@dpsutton ohhh good call. Currently it's 26, but I'm not sure it was in that session. @cjsauer yes
@vinai Definitely looks like some byte-compilation issue, but I haven’t encountered this myself.
Guess you can just forgo the installer and simply clone Prelude. Likely the script is running the wrong Emacs version indeed.
Hi all, I'm currently getting the following error when I run cider-jack-in-cljs
:
error in process sentinel: nrepl-server-sentinel: Could not start nREPL server: Exception in thread "main" java.lang.IllegalArgumentException: No matching ctor found for class java.net.InetSocketAddress
I've tried on two computers and get the same error on both (it's a recent error b/c it was working fine yesterday). Has anyone else gotten this?I think it's related to a change to cider-nrepl
b/c a new version of 0.18.0-SNAPSHOT
was pushed today (https://clojars.org/cider/cider-nrepl/versions/0.18.0-SNAPSHOT)
I’m also having some issues with the new snapshot, can’t get a fresh repl going
@kennethkalmer can you say which version of java you are running?
$ java -version
java version "9.0.4"
Java(TM) SE Runtime Environment (build 9.0.4+11)
Java HotSpot(TM) 64-Bit Server VM (build 9.0.4+11, mixed mode)
same version I’ve been running locally for months
and searching around I only seem to find old issues for Java 9 compatibility, mostly with lein
https://github.com/technomancy/leiningen/issues/2149 this issue runs into the same problem. Are you able to run lein repl
without a problem?
I’m testing it another project, I tend to keep repls running for as long as possible 🙂
blows up the same way, I’m gonna nuke the latest snapshot and run lein offline
Hey all, my emacs seems to instantly disconnect from the figwheel process. Resulting in errors such as
user-error: 'cider-repl-set-ns' needs a ClojureScript REPL.
I’m just switching back to Java 8 for the moment, I have no idea how else to debug this
If there is still any other information or feedback I can provide to help debug the issue, please let me know! I just don’t know where to from here on my own (and I have some work to get done in the meanwhile) 🙂
does anyone know what's up with this error? I'm assuming that Cider 0.18.0-SNAPSHOT changed something
it's very important that the last repl you touched is the cljs repl and not the clj repl
so if you have two repls open (one clj, one cljs) put your cursor in the cljs buffer and then do whatever you need to do
It appears to "break" when I open the web interface of the app. Before I have tried to evaluate anything
I'm on Java 8 and hitting the No matching ctor found for class java.net.InetSocketAddress
too
I threw together a hasty PR: https://github.com/clojure-emacs/cider-nrepl/pull/538
Thanks @hagmonk. Does anyone know of a way to pin melpa package versions? It's a bit insane to be forced to the bleeding edge...my editor has been broken by this for most of the day.
This was caused by cider-nrepl's snapshot being updated in clojars, rather than cider's melpa packages
Since I use clojure-cli, I just added a`deps.edn` to my fork of cider-nrepl and used that instead. with boot and lein it's kinda hard, you really need to wait a fixed artifact to be pushed somewhere
Ah ok. Is there a reason that cider depends on snapshot versions? That seems precarious...
@cjsauer you are using the CIDER from melpa is the bleeding edge version. There is the stable release on melpa-stable
i think it was a bad choice to make melpa the dev version of melpa and melpa-stable the stable branch. I would prefer it was melpa-dev and melpa. But c'est la vie
@dpsutton I'm actually using spacemacs, but looking at the clojure layer I'm not seeing any mention of specific versions anywhere https://github.com/syl20bnr/spacemacs/tree/master/layers/%2Blang/clojure
I've also tried setting package-archives
and package-archive-priorities
to put melpa stable at the top of the list, as described here: https://emacs.stackexchange.com/questions/2969/is-it-possible-to-use-both-melpa-and-melpa-stable-at-the-same-time
No luck there.
Overall, it seems like pinning versions anywhere in the emacs ecosystem is...difficult at best.
https://github.com/jwiegley/use-package there are no linkable section headers but search for "pin" it's at the bottom
for instance, I did C-u C-m M-j
and replaced the default args with: -e '(require (quote cider-nrepl.main)) (cider-nrepl.main/init {:handlers ["refactor-nrepl.middleware/wrap-refactor", "cider.nrepl/cider-middleware"] :port 0 :bind "::"})'
@dpsutton hm interesting...so maybe the clojure layer of spacemacs should pin its use-package
calls to melpa stable?
that sounds reasonable. melpa is the dev version versus melpa stable is the stable releases. seems more likely that the vast majority of users would want the stable
whew...hopefully can get it worked out soon; thanks for the help. Would be lovely to one day have an editor situated directly inside of the clojure ecosystem...I haven't yet bitten the bullet on really learning elisp and its surroundings
spend 5 minutes to learn the debugger, how to jump to definition and a good grep style package and you'll be elisping in no time
the elisp is way easier than figuring out gnarly problems in the cider-nrepl. the feedback loop is tough to debug the tools
"jump to definition" is one of the things that consistently doesn't work for me :) It's always like rolling a dice in emacs .... in elisp or clojure
Cursive's is far more reliable for me - it doesn't require a REPL to be started, and it can jump into jars (which I'm always doing), and decompile the jars or download their source if required
I just tried to test a repro case (org.httpkit.client/get was the last one that failed) but my hacky state with cider-nrepl means that nothing is working properly :/
I have been meaning to check out the Cider support in some of the VSCode plugins. Unfortunately it doesn't appear that any of them have deps.edn
support yet, and I've migrated almost everything over that way
@hagmonk quick tweak to your workaround: had to change :handlers
to :middlware
, and then I also added a bit more middleware for what appears to be a new debugger dependency (bpiel/sayid):
-e '(require (quote cider-nrepl.main)) (cider-nrepl.main/init {:middleware ["com.billpiel.sayid.nrepl-middleware/wrap-sayid", "refactor-nrepl.middleware/wrap-refactor", "cider.nrepl/cider-middleware"] :port 0 :bind "::"})'