@kamuela: you can’t do your sweet sweet JSP programming with the community edition. Also, the JavaScript stuff isn’t in the Community Edition IIRC

@danielcompton: so cljs is off the table?

not off the table, but I don’t think you’ll get as nice interop. But I’ll let cfleming give you the official word on that, as I might be wrong. Webstorm has the JS stuff, so you might be able to use Cursive in Webstorm for CLJS stuff

Pretty sure Cursive doesn't work in Webstorm yet.

@kamuela: @danielcompton: @meow: Right, Cursive doesn’t work in WebStorm yet, although I hope it might soon. But for Clojure and cljs there’s no difference between Community and Ultimate - Cursive doesn’t use the JS integration in IntelliJ at all.

@cfleming: is there an existing issue related to the debugger where execution moves on only after hitting resume multiple times?

@moizsj: I’m not sure if there’s an issue for it, but it’s a known quirk.

It’s because you get several executable statements on the same line.

That can also happen even though it doesn’t look like it in your code because of macroexpansion.

Destructuring is a common cause of this, for example.

ah i see..so it moves on only after the underlying java statement have all been stepped over?

I plan to investigate to see if I can stop that happening, but I haven’t done so yet, and it’s also not clear whether that would be desirable - if in your code you actually have multiple expressions per line you might want to stop there.

@moizsj: Well, it’s bytecode rather than Java, but in essence yes

@moizsj: If you don’t mind watching talks I spoke at Clojure/West about the debugger last year and talked about that and many other quirks of debugging Clojure

@cfleming: will defintely revisit it. have seen it once but in a hurry. thanks!

is anyone aware of a keyboard shortcut to extend selection to left or right, staying on the current structural editing level?

so say I have the following structure:

{:foo    {:bar 1}
 :baz    {:quux 2}
 {:a :b} {:asdf 3}

and I position the caret onto :quux, extend selection thrice so {:quux 2} is selected

and then I want to include :baz in the selection

but not anything else from the main map

@imre: There isn’t one right now. You can use the “sticky selection”, which is sort of like the Emacs mark

But I’m planning to add a “extend selection to next/previous form”, which CCW has and a lot of people like.

great to hear that

That’s in the very-short queue

I'll have a look at sticky but I assume it doesn't obey structural editing rules s

Well, you can combine it with the structural movement.

i.e. mark, move over right form

“Toggle Sticky Selection” is the action

just tried that, it could be useful yeah

I'll bind it to something and try

But the grow selection commands are what you really want, I think.

And they’ll be more important once I implement extract method.

yep

thanks for that, Colin

No worries

@cfleming @danielcompton thank you both for letting me know

@cfleming: that mark-and-go thing works nicely