This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (38)
- # announcements (1)
- # aws (1)
- # beginners (195)
- # boot (1)
- # business (3)
- # cider (100)
- # cljsrn (37)
- # clojure (99)
- # clojure-russia (69)
- # clojure-switzerland (1)
- # clojurescript (120)
- # datavis (26)
- # datomic (23)
- # devcards (4)
- # editors (38)
- # hoplon (18)
- # ldnclj (27)
- # lein-figwheel (28)
- # off-topic (50)
- # om (329)
- # onyx (255)
- # portland-or (1)
- # re-frame (8)
- # reagent (18)
- # spacemacs (5)
- # testing (1)
although that is not the main purpose there but i guess @magnars ’s parens of the dead uses emacs/cider
@benedek and @bozhidar, thanks for the advice! I already had Parens of the dead lined up. i'll probably watch that after i get through some intro clojure material.
stuart halloway spoke about alien super powers coming after 6 months’ practice or so in one of his talks. Parens of the Dead is a demonstration of those alien super powers
@bhauman: just finished setting up my relatively small clj/cljs/reagent project following https://github.com/bhauman/lein-figwheel/wiki/Using-the-Figwheel-REPL-within-NRepl in emacs/cider amazing experience so far, gives me what i really missed (eg had to work with two repls kinda) together with @malabarba /expez ’s work that cider basically routes evals to the right repl it is just mind blowing.
and if anything gets broken remove clojure-mode and cider and then install them on clean
how do you reinstall a package in emacs? Do you have to manually delete it from the file system?
M-x package-list-packages then mark the packages with
D in the buffer then
X to execute
I was afraid I was doing something wrong, but looks like that is the default behavior
i know it is painful but I guess emacs package manager needs some fixing not really the package… 😉
if i run into problems after an upgrade I still remove both and install clojure mode first. mind you i usually run with latest snapshots
I've been upgrading daily for about two years now, I don't think I've had more than a week of problems
tbh I don’t. only I am aware that is a regular problem for those who use the latest snapshot (based on bugreports gitter etc)
@bhauman: if we get our act together, 0.10.0 should be out during decembre. But that's not a promise.
And no, socket-repl is not part of it. It's currently just something on our minds. Nobody has stepped up to support it yet.
if I understand how things look socket repl wise: we need something like nrepl implemented around the socket repl before we can roll with it too
@roberto: @benedek The problem with Emacs' package manager is Melpa. Melpa sort of assumes its users will stay always updated, so its version numbers mess with dependencies, and that causes outdated dependencies. You can usually avoid problems by just keeping your packages regularly updated. You can do that with
M-x list-packages then
there is this: https://github.com/puredanger/replicant but it is more a proof of concept than a real thing
in particular, I think
dash was a package that caused a bit of issues with Melpa. And cider no longer depends on Dash, so things should be better on that front
geez, well printing in cljs works it just prints before the prompt that sent the print message
On the topic of the Socket repl... It's looking like the easiest way for cider to support it will be by somehow mimicking an nrepl server through it.
But maintaining two separate ways of interfacing between clojure and Emacs would be insane IMO
Another issue is that the Socket repl is completely bare bones, so we'd have to manually do a lot of stuff that currently nrepl does for us. Though I don't know if that's just because it's new or if it's intended to be like that.
- @benedek and @malabarba already said pretty much everything there’s to say about the socket repl support - basically we’ll need some way to multiplex a couple of socket repl connections (one for evaluation and one for tooling stuff) and we’ll still need to ship our extra deps providing the tooling
the biggest gain for supporting the socket repl will likely be better clojurescript support
- we’ll have to break down
cider-nrepl into two packages - some library holding the tooling functionality and the middleware itself
- we’ll have to come up with something like
replicant which people will have to install if they want to use the socket repl
I’d really love to us to support it, but it’s not super high on my persona todo list
as this is quite a lot of work and the benefits of supporting it are not exactly huge
@roberto do you mean just load the entire project or actually compile it into a jar file
I’m using component, and everytime I reload the entire system, I need to compile every individual project again