Fork me on GitHub
#cursive
<
2016-02-01
>
danielcompton00:02:08

@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

Kamuela00:02:11

@danielcompton: so cljs is off the table?

danielcompton00:02:00

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

meow01:02:39

Pretty sure Cursive doesn't work in Webstorm yet.

cfleming09:02:48

@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.

moizsj10:02:35

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

cfleming10:02:09

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

cfleming10:02:25

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

cfleming10:02:41

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

cfleming10:02:00

Destructuring is a common cause of this, for example.

moizsj10:02:22

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

cfleming10:02:58

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.

cfleming10:02:19

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

cfleming10:02:04

@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

moizsj10:02:02

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

imre10:02:12

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

imre10:02:22

so say I have the following structure:

imre10:02:09

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

imre10:02:10

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

imre10:02:24

and then I want to include :baz in the selection

imre10:02:52

but not anything else from the main map

cfleming10:02:08

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

cfleming10:02:33

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

imre10:02:49

great to hear that

cfleming10:02:02

That’s in the very-short queue

imre10:02:17

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

cfleming10:02:49

Well, you can combine it with the structural movement.

cfleming10:02:04

i.e. mark, move over right form

cfleming10:02:39

“Toggle Sticky Selection” is the action

imre10:02:58

just tried that, it could be useful yeah

imre10:02:13

I'll bind it to something and try

cfleming10:02:24

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

cfleming10:02:36

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

imre10:02:48

thanks for that, Colin

Kamuela14:02:18

@cfleming @danielcompton thank you both for letting me know

imre14:02:03

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