@benedek: I tried lein upgrade but was told that I would have to delete my 2.6.1 batfile, which I take means that I'm already on the newest version

I still can't lein jack-in, after reinstalling Spacemacs, updating Spacemacs, updating packages, putting meaningful stuff in ~/.lein/profiles.clj, emptying the same... Can't lein upgrade further...

Still get the same stacktrace (whose buffer annoyingly vanishes if I try to navigate to it to copy)

I'm on (emacs-24.5.1) (spacemacs-0.105.14)

try to clean your profiles.clj. based on the info you posted you use cider/clj-refactor versions which don't need tampering with profiles.clj anymore

And most likely you have a problem because of a transient dependency from profiles.clj - guessing here ofc

@benedek: right now, my profiles.clj is {:repl {:plugins [ ] :dependencies [ ]}}

And I get the same result 😕

Weird

what does lein --version tell you?

@benedek: Leiningen 2.6.1 on Java 1.8.0_65 Java HotSpot(TM) 64-Bit Server VM

this looks ok

yeah It's very puzzling.

what does lein deps :tree say?

Also try to reproduce with a newly created empty project

lein deps :tree says:

c:\dev\clojure\projects\linden>lein deps :tree
warn
 [clojure-complete "0.2.3" :scope "test" :exclusions [[org.clojure/clojure]]]
 [org.clojure/clojure "1.8.0"]
 [org.clojure/tools.nrepl "0.2.6" :scope "test" :exclusions [[org.clojure/clojure]]]

A fresh project generated with lein new <name> has the same error.

@reefersleep: I fear that the problem could be with windows. I actually don't know how does it work in windows, but it's just a guess

I'm pretty sure I can do a clean install of spacemacs in OSX and configure cider afterwards(by following the 2 steps we discussed yesterday)

@reefersleep: also, is it lein jack-in? Not like SPC : cider jack in ?

looking at the README there's talk about "var tracing" and "namespace tracing", but it doesn't explain what that means...

can anyone explain what that does or what you would use it for?

@thiagofm: To be clear, my clean reinstall of spacemacs consisted of backing up my .spacemacs, deleting .emacs.d, cloning the master branch of spacemacs into .emacs.d, then starting up emacs and letting spacemacs download everything

I'm talking about cider-jack-in (SPC m s i)

Okay

@thiagofm: Everything was working fine until I started messing about with profiles.clj yesterday

If you do a clean install, add the clojure package to .spacemacs, do the two steps config and then restart emacs and try to do cider-jack-in it doesn't work?

I can give it a clean go and see Why do I need the clojure package, though - doesn't spacemacs automatically download this upon SPC m s i?

s/package/layer

Add the clojure "layer" to .spacemacs

It's there

Pasted in from my backed up .spacemacs

I would do stuff 100% from scratch in that case

Because perhaps it could be a problem on your .spacemacs, you never know, so it's good to narrow down things a bit

aye

I'll give it a go.

👍

@thiagofm: Same result. (When you talk about the two steps config, you are referring to adding

{:repl {:plugins [[cider/cider-nrepl "0.10.0-SNAPSHOT"]
                  [refactor-nrepl "2.0.0-SNAPSHOT"]]
        :dependencies [[alembic "0.3.2"]
                       [org.clojure/tools.nrepl "0.2.12"]]}}

The only manipulation I did unto .spacemacs was to add the clojure layer.

@plexus it's a general Clojure thing. It prints all calls to the function on the repl.

Actually, it was in an attempt to get to know cider-debug that I managed to bodge up my REPL. I was interested in trying out tracing as well. What timing

@malabarba: thanks!

@malabarba: Thank you for your work Do you think I should open an issue regarding my problem - and if so, where do you think it belongs? It seems like a spacemacs issue, but it might actually belong with cider or cider-nrepl...

File it under cider, with all of the information you have so far. Also Make sure you're using a clean profiles.clj.

Thanks @malabarba

I've tried with both a clean and tainted profiles.clj, for the record 👌

😉 👍

I followed the advice in the Troubleshooting part of the Cider README and activated toggle-debug-on-error, and managed to catch something meaningful

could not start nrepl server: clojure.lang.Compiler$CompilerException: java.io.FileNotFoundException: Could not locate mranderson047/toolsnamespace/v03v0_alpha3/clojure/tools/namespace/parse__init.class or mranderson047/toolsnamespace/v0v3v0_alpha3/clojure/tools/namespace/parse.clj on classpath: , compiling:(refactor_nrepl/core.clj:1:1)

It doesn't help me in a google search, but I think I saw some trouble with mranderson mentioned somewhere. Does anyone recognise this?

The "Troubleshooting" section also mentions looking in the *Messages* buffer or the *nrepl-messages* buffer. I can't find these. Does anyone know how to reach them?

@reefersleep: should be on SPC p b or C-x b

Looks like a problem with clojure/java/classpath

which I have absolutely no idea how to fix 😆

@thiagofm: SPC b b <name_of_buffer>

Works for me

Yes, sorry

So I have the whole stacktrace. But it's not very interesting.

😞

Perhaps rm -rf . and curse java? Not sure if I can help more

Do you also have the same error when you run lein repl from the terminal?

nope, lein repl is healthy

Do you have nrepl in your project as a dep?

No

I've tried with a clean lein new, too

I wonder if that helps

Hm, I have a project that should work, if you wanna try: https://github.com/thiagofm/haxlife

You have to press , s I

cider-jack-in-clojurescript

It's weird, you probably have exactly the same config as me

in a different OS

cloning

I hit the same exception

After downloading some deps

https://github.com/clojure-emacs/cider-nrepl/issues/273 @reefersleep ?

Looks like exactly the same error, but I have

c:\dev\clojure\projects\haxlife>lein --version
Leiningen 2.6.1 on Java 1.8.0_65 Java HotSpot(TM) 64-Bit Server VM

But maybe I should attempt to reopen the issue

?

❯ lein -v Leiningen 2.5.3 on Java 1.8.0_72 Java HotSpot(TM) 64-Bit Server VM

yeah

also downgrade your lein version and try again

Get the same output with SPC m s i after switching to 2.5.3

is there a key command to compile my code and see linter warnings? or does clojure not work that way?

@fommil: I don't think it "normally" works that way, although there are many ways to work with Clojure. My way is to open a REPL, write code in my clj/cljs/cljc file (whichever I'm working on), experiment in the REPL, refine code in the file, then, when I have something that I think works, start loading the file's ns into the REPL so that I have access to all defns and defs from the REPL. Then I can experiment with the stuff I have in the file.

I have not used any linting functionality that I know of.

I use Spacemacs and Leiningen. When I want to run my project as a whole, I use the appropriate Leiningen or Java command.

I have a dark theme (darcula) and when I get a stacktrace or test failure the default faces are all dark text on a white background. Is there a built in dark theme for this or am I going to have to create my own faces?

@fommil: I believe that there are non-darcula dark themes which are more suitable, but I haven't seen them myself At least there's Borealis, which Colin Flemming, writer of Cursive, recommends: https://github.com/Misophistful/borealis-cursive-theme

(I assume you're using Cursive)

@reefersleep: I don't want a new theme, I want cider to stop using its own light theme defaults for stacktraces

no I'm using Emacs

@fommil: Then I have no experience that could help you

@thiagofm @benedek omg, I solved the problem. And it was really, really stupid. I, myself, have found a bug in Leiningen for Windows, reported it and submitted a pull request that leaves comments in lein.bat and README.md warning that you should not have a LEINJAR environment variable as well as a different reference for Leiningen on PATH_, as this might mess things up. And here I am, with a LEIN_JAR environment variable still set.

Guess I didn't clean up after experimenting while sorting out the Leiningen issue with HyPiRiOn.

Removed the LEIN_JAR, and now everything is good. Damn!

@malabarba: We'll skip that issue at Cider, then. 😄

Haha nice one!

@reefersleep: I TOLD YOU, WINDOWS!!!!

@reefersleep: it's great that you finally found the solution, you've been in quite a battle, I remember your struggle from yesterday. A real clojure warrior!

@fommil cider doesn't force light themes anywhere. In fact, I use a dark theme and never noticed that issue.

@reefersleep congrats on tracking down that bug. You deserve a prize.

@fommil its possible you have some face customisations saved in your custom file. It's also possible you have more than one active theme, and they're conflicting. It's also possible the theme you're using is a little buggy with those faces (though it's unlikely).

@thiagofm: Yeah, woooo

@malabarba: Put my mark on Leiningen, I think that's a pretty cool prize!'

So, after all this malarkey, I finally got to test out cider-debug, like I wanted to... Damn sweet, that!

I should have known about this long ago!

😉 🍻 🍻