Fork me on GitHub
#cider
<
2016-07-28
>
seancorfield01:07:50

@bja: Yeah, that happened to me today after I rather foolishly updated all my Emacs packages… How did you solve that?

danielsz02:07:00

@seancorfield: I just change my config to the snapshot versions.

danielsz02:07:55

cider and cider-nrepl both point to the snapshot version. No mismatch.

seancorfield02:07:32

@danielsz: Not quite sure what you mean...

danielsz02:07:11

Maybe I didn't understand the problem.

seancorfield02:07:09

When I try to jack in, cider.el tries to specify a (Boot) dependency of cider-nrepl 0.14.0-SNAPSHOT but no such version exists.

seancorfield02:07:06

I installed Prelude a while back and everything was working fine. Today I decided to update the packages in Emacs (to get the latest version of cider primarily), and since then, it tries to inject cider-nrepl 0.14.0-SNAPSHOT.

seancorfield02:07:54

In addition to the problem that Prelude doesn’t seem to fully start up (it didn’t load my prelude-modules.el file nor my personal/custom.el file).

seancorfield02:07:51

I even blew away .emacs.d completely and re-cloned the latest Prelude but that’s still broken (so it’s got to be something in one of the later elpa packages it relies on I guess?)

danielsz02:07:15

@seancorfield: Ah, I see. In that case, if you're interested, I can tell you how I avoid those problems, but I don't think you'll like it. 🙂

seancorfield02:07:34

Don’t use Prelude? 🙂

danielsz02:07:42

Bingo! 🙂

seancorfield02:07:13

It’s been working fine for ages… but of course I figured a package update would be a good idea 😐

danielsz02:07:15

And another thing: don't jack in neither.

danielsz02:07:46

Package update is a good idea.

danielsz02:07:01

I always update my packages.

danielsz02:07:20

But I launch my nrepl externally, not from emacs.

seancorfield02:07:31

Yeah, well, that is what broke my Emacs setup so I’m not sure I’m finding your advice very helpful right now 🙂

seancorfield02:07:51

I always launch my nrepl via Emacs. Always have done.

danielsz02:07:17

I knew you wouldn't like it.

danielsz02:07:21

If you launch the nrepl externally, you avoid the problem of injecting a non-existent Cider-nrepl.

danielsz02:07:24

Also, your Java process is independent from the Emacs session. Big win!

seancorfield02:07:15

What I want right now, is some insight into getting Prelude working properly after the package update… based on the error messages I’ve managed to find, it’s a problem with projectile...

seancorfield02:07:28

projectile-go-function seems to be the problematic symbol...

richiardiandrea02:07:49

uhm I have not updated projectile so maybe that's what saved me

richiardiandrea02:07:01

I can give you the commit I am at..

seancorfield02:07:24

Yup, definitely a bug in projectile… they reference a Go-related function that isn’t defined and that stops the compile of everything downstream...

richiardiandrea02:07:02

cool that you solved it then

seancorfield02:07:33

Now I still have to solve the 0.14.0-SNAPSHOT injection 🙂

danielsz02:07:45

boot repl etc. in the terminal + cider-connect is one way to solve it.

danielsz02:07:31

I'm not trying to preach, though.

seancorfield02:07:01

@danielsz: please stop suggesting that.

danielsz02:07:28

@seancorfield: Please ignore my suggestions.

seancorfield02:07:30

Well, I "solved" the CIDER version injection by editing cider.el and changing the defconst cider-version but it looks like it ought to be able to deduce it from somewhere but it’s not clear to me how/where it figured that out.

dpsutton03:07:46

hmm. looking at what's on melpa, somehow a version was released specifying the new development version

dpsutton03:07:09

i don't konw what triggers updates on melpa

dpsutton03:07:15

but that's definitely a problem

seancorfield03:07:14

I wonder if @bozhidar just forgot to release 0.14.0-SNAPSHOT to Clojars along the way? That would also solve the problem 🙂

ska12:07:41

Hi. Has anyone ever encountered issues with the mouse after running cider-jack-in?

ska12:07:25

When I open a clojure buffer, everything works fine. I can also M-x cider-mode and all is well. But after jacking into a project I can not select text reliably with the mouse anymore.

ska12:07:13

Doubleclicking works, but dragging only works when start and end are either at eol or bol

ska12:07:30

Totally weird 🤔

ska12:07:36

Oh, when I set cider-use-tooltips to nil, all is well.

ska12:07:45

I can probably live with that.

malabarba13:07:40

@ska please report that as a bug 😉

malabarba13:07:52

> I wonder if @bozhidar just forgot to release 0.14.0-SNAPSHOT to Clojars along the way? That would also solve the problem 🙂 @seancorfield probably. Just report it and we'll fix it ASAP 😉

benedek16:07:56

@seancorfield: as @malabarba said. it is basically an error in our part (eg not releasing middleware snapshot together with cider emacs package release)

benedek16:07:54

alternatively you can stop cider autoinjecting with cider-inject-dependencies-at-jack-in to nil

benedek16:07:30

and then you need to specify the deps the old way (in your profiles.clj or boot equivalent)

benedek16:07:15

suppose if you use the 0.13 middleware cider will complain but mostly work. (have not tested)

dpsutton16:07:16

I mentioned to Malabarba that perhaps we could switch over to a git flow style development, and he brought up a good point that that would be duplicated the functionality that melpa-stable offers over melpa. Which is to say, running cider from melpa is necessarily a preview build

dpsutton16:07:29

I didn't know that and I suspect that most people didn't know either.

dpsutton16:07:51

I kinda wish that rather than melpa and melpa-stable it was melpa-snapshot and mela (stable being the default)

dpsutton16:07:11

but malabarba had pretty good argument that if you want stability and pure releases, that is already available

benedek16:07:02

well, yeah, that is why our sample config uses melpa-stable

anmonteiro17:07:15

@bozhidar: updated cider from Melpa and it’s complaining about a missing cider-nrepl 0.14.0-SNAPSHOT on clojars

seancorfield17:07:50

@benedek: It just caught me out because I rely on Prelude and I decided to update all my packages (which Prelude’s docs encourage you to do! 🙂 )

seancorfield18:07:21

I spent more time tracking down and fixing the Projectile issue than the CIDER one, to be honest. I was just hoping there was a way to "encourage" CIDER to use the latest stable release rather than modify the code (I suspect it can’t figure things out from our Boot file since pretty much everything is computed dynamically depending on which task is being run).

seancorfield18:07:57

If Prelude used melpa-stable by default, I suspect I would have been fine?

benedek18:07:46

tbh we (meaning the cojure-emacs team) should release a snapshot of both cider client code and middleware as part of the release cycle. but i am also not doing the releases so that is up to @bozhidar and @malabarba I guess and they tend to be pretty busy nowadays

benedek18:07:59

melpa-stable: indeed you would

benedek18:07:13

but the above workaround should do the trick too

benedek18:07:29

until the 0.14-snapshot is out for the middleware

seancorfield18:07:19

Well, we no longer specify the middleware in our Boot config for the REPL task (because CIDER auto-injects it) so it would be more disruptive to change that across the team than to just patch cider.el 🙂

seancorfield18:07:42

And right now, no one else was adventurous enough to update their Emacs packages...

seancorfield18:07:16

Although modifying Prelude to use melpa-stable locally sounds like a good idea...

benedek18:07:14

fair enough. perhaps forcing a certain version (eg making you quick fix a config feature) may make sense… not sure tho...

benedek18:07:03

feel free to record an issue on github with this proposal if you think it worths it to see what the team thinks...