This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (19)
- # announcements (4)
- # beginners (22)
- # boot (76)
- # cider (92)
- # clojure (235)
- # clojure-berlin (3)
- # clojure-germany (1)
- # clojure-italy (8)
- # clojure-japan (18)
- # clojure-russia (26)
- # clojure-sg (1)
- # clojure-uk (25)
- # clojurescript (55)
- # code-reviews (7)
- # core-async (53)
- # datomic (13)
- # euroclojure (63)
- # jobs (39)
- # ldnclj (45)
- # off-topic (9)
- # om (7)
- # onyx (6)
- # reading-clojure (1)
- # reagent (5)
- # yada (22)
sometimes I have issues with cider in some projects, when cider fires up correctly
something to do with the order things are loaded I suppose, but am I doing something wrong in general or that should work?
however it's maybe related with https://github.com/clojure-emacs/cider/issues/950? what would be a workaround maybe anyway?
a simple project + those steps in generally the quickest path to a problem’s solution
but it might be related to https://github.com/clojure-emacs/cider/issues/1144
GNU Emacs 126.96.36.199 (x86_64-pc-linux-gnu, GTK+ Version 3.10.8) of 2015-05-19 on lcy01-07
but I actually saw the same issue with another project of mine, if in the repl I do (clojure.test/run-all-tests) it works
so it loaded correctly I just can't load files and refresh, in my own project I more or less solve by loading files in a certain order
btw, as I mentioned on the other ticker I wonder if the same problem happens if you just invoke
tools.namespace.repl/refresh from the REPL
cider-refresh is a wrapper around this function (to some extent - it actually uses lower-level code to provide better editor experience)
code-maat.cmd-line> (tools.namespace.repl/refresh) code-maat.cmd-line> code-maat.cmd-line> (+ 1 2) code-maat.cmd-line>
mm and now I'm getting out of memory because I have 4 java processes eating all the memory..
when I kill the cider buffer it doesn't seem to kill the process is that normal?
nrepl-server run *nrepl-serve... /dev/pts/21 /bin/bash -c /home/andrea/.local/bin/lein repl :headless nrepl-server<1> run *nrepl-serve... /dev/pts/35 /bin/bash -c /home/andrea/.local/bin/lein repl :headless nrepl-server<2> run *nrepl-serve... /dev/pts/36 /bin/bash -c /home/andrea/.local/bin/lein repl :headless nrepl-server<3> run *nrepl-serve... /dev/pts/37 /bin/bash -c /home/andrea/.local/bin/lein repl :headless
and last thing which annoys me (general Emacs issue maybe) is that I can't get to the source of an Elisp function
(cider-refresh &optional ARG1) Cannot open doc string file "/home/andrea/.emacs.d/elpa/cider-20150629.637/cider-interaction.elc"
package management is a bit fucked-up and it’s generally best to restart Emacs after upgrading packages
the documentation lookup doesn’t work because it’s trying to access files from the older installation of cider you had prior to updating it
actually I would just like to not upgrade everything all the time and just upgrade on stable new versions
I guess I just have to kill the nrepl buffer to kill the java process and not just the cider one is that right?
@andrea.crotti I don't know if this matters here, but there are two buffers, the repl and the nrepl. I always have to kill both in order to kill the process.
Cider should probably hook the two buffers together so that killing one kills the other too. What do you think @bozhidar ?
Also @andrea.crotti , one way to only get stable upgrades is to not use Melpa, only Melpa-stable
when you use
nrepl-server buffer is the one being backed by the process used to start the nrepl server (e.g.
the REPL buffer is backed by the actually connection between cider & the nREPL server
maybe someone knows here, is there a valid reason why if I write "; TODO: something"
One ; is for end-of-line comments. Two ;; is for indent-with-code comments. And ;;; or more is for beginning of line comments
is there a way to make cider work with clojurescript? I’m a total newbie, been using emacs for about 4 months.
@roberto: well, it works with ClojureScript out-of-the-box (piggieback & figwheel are both supported), but not all of the standard features work with cljs (at least not yet)
OK … Clojure is my first JVM language so I’m not super familiar with maven, etc. How might I go about getting the source artifacts for a library dependency and making sure they are in the classpath? Right now it looks like I only have the compiled class files in my local Maven.
@enn Java IDEs, such as Eclipse, will automatically grab source code the moment you ask to look at it.
I never did anything special in that regard, but I can visit the source of any clojure Var, for instance.