@kenny Cursive already does something like that - do you mean evaluate an individual assertion?

i.e. an is check or something similar?

Yes

Which could (probably is) be surrounded by a let block.

I'm having a little frustration...

created a lien project, added a local repl configuration

when I start the repl, it can't find the .core namespace

@kenny So that gets a little tricky because of fixtures and the like

And also cases such as having your assertion in a loop and so on.

But it’s something I’d really like to have myself, I’ll see what I can do.

@tghali How did you create the lein project? On the command line or within Cursive?

within cursive

Ok, can you post a screenshot of your REPL run config?

Looks good - what’s the error you’re receiving?

While having custom behavior for tests would be cool, the simple use case should be covered. Example:

(let [x 1
      y 1]
  (is (= 2 (+ x y))))

phooey.core:

(ns phooey.core) (def something "wowee")

in repl:

Connecting to local nREPL server... Clojure 1.8.0 nREPL server started on port 53981 on host 127.0.0.1 - <nrepl://127.0.0.1:53981> wowee CompilerException java.lang.RuntimeException: Unable to resolve symbol: wowee in this context, compiling:(/tmp/form-init5376564895231553441.clj:1:4272) (str "sdf " wowee) CompilerException java.lang.RuntimeException: Unable to resolve symbol: wowee in this context, compiling:(/tmp/form-init5376564895231553441.clj:1:1) ns => #object[clojure.lang.Namespace 0x6b1ae6c2 "user"] (find-ns 'phooey) => nil (find-ns 'phooey.core) => nil

@kenny Right, but something like this is harder:

(doseq [x [1 2]
        y [1 2]]
  (is (= 2 (+ x y))))

@tghali So the problem is that you haven’t loaded your namespace - Cursive doesn’t load namespaces automatically.

@tghali Tools-&gt;REPL-&gt;Load file in REPL before you start evaluating should do the trick

@kenny I can special case your simple case, but then it’s more complex than just a case of ensuring all the symbols resolve.

TBH just having this ability for a let would be huge. I think loops are more of a special case

(that case is probably ok actually, it’ll just run the is multiple times, but there are plenty of trickier cases)

@kenny Ok, I’ll try something along those lines and see what I can come up with.

Also would be cool to have the values of the let displayed next to their definition (like Light Table), but I recall you saying redrawing the editor in IntelliJ was hard/not possible.

Again, it’s actually relatively simple in simple cases. It gets difficult when your results are collections.

Because it becomes too large to display?

Also, not sure if this precisely covered but for clarification.. It would be awesome to be able to individually evaluate let bindings (without actually being in the body of the let):

(let [a 1
      b 2
      c (+ a b) ;; <— cursor is after last parens
      d 4])

Yes, @denik’s original case would cover that, with the slight caveat that:

(let [a 1
      b 2
      c (+ a b) ;; <— cursor is after last parens
      d (launch-missiles)])

Actually, thinking about it that’s a little trickier since the return value of the let is not what you want - that would be a little harder.

I’m actually planning some more sophisticated manipulation of this kind of form for extract function, since in a lot of cases you’d like intermediate local let bindings moved into the extracted function too.

@kenny Sorry, missed your earlier question about collections display - yes, the restriction is that I can only display a single line at the end of the code line.

So the only available space is whatever space is left at the end of the line after the code, simple values should be ok but collections will be tricky.

That super awesome. That feature would be HUGE! 😀

@cfleming , was there a time when the core namespace was loaded and set as current ns on repl launch? I have an older project with a local repl that behaves that way (very conveniently).

@tghali There’s no way to tell a REPL what the “main" namespace is

Also, it takes no time at all to load and switch into the namespace you want. Just set keybindings for load and switch commands and you’ll be set 😉

@kenny - I just found the missing ingredient. I needed :main phooey.core in my defproject.

thanks for pointing out keybindings; I'll look into them. I'm sure they can be very useful.

In clojure file, when I type ; on a non-empty line, this semi-colon is shifted to column 61. I just want to it stay where I typed. I’m not sure if it’s IntelliJ thing or Cursive thing. Anyone knows how to turn this off?

@tap Settings-&gt;Editor-&gt;Code Style-&gt;Clojure-&gt;General-&gt;Comment alignment column. Setting that to 0 will do what you want.

@cfleming : I have an application written storm. I really want to debug some of the lower level startup code in Storm that is written on clojure. I have a remote debug jvm and I am connected to that vm with Intellij and Cursive. That is hitting breakpoints but none of the symbols are resolving, and the step throughs seem to be java byte code step throughs. I am not stepping through at the Clojure level.

I have spent a bit too much time on this already. Those applications are starting with nrepl running from nrepl.jar file.

But I am not sure the debug port, the process does not have any ports other than the ones for jmx, already in the java command line.

I also need to debug at startup. so I have -agentlib:jdwp=transport=dt_socket,server=y,address=8100,suspend=y which is halting until I connect with initellij debugger.

Can I get the Clojure symbols and step through with Clojure using lines?

This is a link to the nrepl jar file: https://github.com/clojure/tools.nrepl

@bradrhod Cursive uses the JDI under the hood, which actually debugs Java bytecode. It’s difficult to get e.g. expression level debugging with it.

I spoke about this at Clojure/West last year, and I discussed a bunch of the problems with it there.

The symbol resolution should work, with the caveat that Storm is extremely macro heavy and Cursive struggles with it.

Do symbols like defn resolve ok? Which are some of the symbols that do not resolve?

I do not think any variables are resolving.

I saw your talk on Clojure/West and have a note to look at it again.

thanks for all your help.

bradrhod When you say the symbols are not resolving, what do you mean? Do you mean local variables in the debugger view? I was referring to the editor, where everything except nimbus appears to be resolving correctly.

@bradrhod ^^

correct

in the debugger. Symbols

If nothing can be done, that is fine. Just wanted to ask the question.

You’re seeing no symbols where the debugger is currently stopped in that image because it’s stopped in a class initialiser (<clinit> in the stack frame)

It hit the break point on line on 437

(defnk launch-process [command :environment {}]

I think it is showing the javabytecode decompile symbols there, correct?

Could be, can you send a screenshot of what you’re seeing when it’s stopped at that line?

@bradrhod ^^, sorry, forgot to ping you again