@shaun-mahood No, they’re really just there for completeness. The simple close-bracket forms jump to the end of the next closing form of that type, but there’s a good argument to be made that they should probably all just jump to the nearest closing delimiter of any type.

So:

{:foo [:something (do-something|)]}

Where | is the caret

Right now, if you press ) it’ll jump over the paren, if you press ] it’ll jump to the closing brace, and if you type } it’ll jump to the end.

It would probably make sense for ) to just jump to the next one regardless of type, and that would then free up ] and } for other things, or they could all work the same way.

The close-and-newline versions just do that, and then add a newline and indent.

I suspect it is pretty irrelevant what the exact behaviour is - I only care at all because I'm messing around with a stupid customized layout so I'm trying to map all the structural stuff and shortcuts and see if I can use them more. I've been comparing paredit in Emacs, smartparens (spacemacs default), and the Cursive implementation just to see what things do.

Interesting - if you see anything you like that Cursive is missing, do let me know.

I’d like to try lispy out at some point too, although the learning curve looks formidable.

We need a yak-shave emoji here.

Here'a my current iteration - kind if fun but I suspect not the most useful thing I've ever done. https://github.com/smahood/ergodox-infinity-layout/blob/smahood-layout/README.md

That’ll do, I guess

I think it should be a green yak though :)

@cfleming: Lispy looks interesting, I really like the part of documentation with the reversible commands - one of the parts of learning emacs-paredit/cursive-paredit that is pretty unintuitive to figure out.

Yeah, I’ve actually considered something like a touch-typing tutor but for paredit, with exercises designed to teach you how it works.

I like the context-sensitive short commands in lispy.

And yes, the doc is really good.

The world of editing lisps has got to be a pretty unending source of ideas for you to implement in Kotlin :)

Haha

Indeed

Although all the paredit stuff is in Clojure 🙂

If you decide you are coming to the Conj I'd be super interested in a Kotlin talk related to your work - I suspect I'm not the only one.

Yeah, that would be interesting to give - unfortunately I’m unlikely to go to the conj this year.

I almost tried to swing Euro Clojure this year but timing didn't quite work. It'll be less fun without you there.

Thanks - it would be great to catch up again. The border circus is a bit off-putting, though.

I haven’t 100% decided yet.

Yeah. I changed my travel plans a bunch of times to avoid it already. Transatlantic laptop stuff is just insane though.

No doubt.

I’m looking forward to a Clojure North in Canada 🙂

Our local clojure meetup has 2 regulars so we're almost halfway there to a big conference!

I think there's a reason clojure remote was born in Canada, though Toronto sounds like there are quite a few devs there.

Yeah, IIRC Yogthos said they regularly get 30 or so, all working with Clojure.

can I start cursive remote repl in debug mode? the option is disabled

Say, when I'm calling a function with the arguments on a new line, Cursive formats the second line with two spaces, like this:

(foo
  bar)

(foo
 bar)

I looked in the code style settings, but I don't see an obvious way to set this, is there a setting I'm missing?

does One Space List Indent not do what you are looking for?

@timgilbert

I'm not able to find that setting, where do you see it?

Away from computer but I think it's editor>code style>clojure > general tab

Aha! Found it, thanks @zylox!

No problem

It's a little weird that test output is printed in red even when the tests pass, no?

what output

i dont have any red output

@nwjsmith Only stderr should be printed in red.

@psalaberria002 No, because the remote REPL doesn’t start the process it connects to (which is required to start in debug mode). If you want to debug a process you’re connecting a remote REPL to, you have to a) start it in debug mode, b) connect the remote debugger, c) connect the remote REPL.

Ah, thanks that makes sense