thanks for creating this!

if anyone wants to help add parinfer to editors/repls, wrote a guide here on how to do it: https://github.com/shaunlebron/parinfer/tree/master/lib

I’ll subscribe to notifications here so I can answer questions

Hello shaun

I can help answer questions about editor integration

hi dominic

didn’t understand what you said here: https://twitter.com/severeoverfl0w/status/669238565545615360 might be able to help with more details

@shaunlebron Neovim's built-in autoindent isn't running, when the parens are closed, because, well for most people that's what is desired!

But, if parinfer has an override, I just need to double check that nvim-parinfer.js is supposed to be shifting the cursor in accordance with parinfer, (as opposed to it being a parinfer issue)

Does that make any sense?

Hi Chris, Shaun :)

hello

hey there

yeah, dominic, it’s still a little vague

are we talking about Indent Mode?

if you could create a concrete case for what you’re expecting (current text -> keystroke -> expected output), I can better understand

@shaunlebron: I'll give it a go.

@snoe do you know what I'm talking about by any chance?

“when the parens are closed”, they are always closed in Indent Mode, right?

@shaunlebron: I'm not sure nvim-parinfer.js supports anything outside indent mode anyway.

Tell you what, @shaunlebron I'll try the replete example in neovim.

yeah, replete’s example would not produce the same behavior in Indent Mode

but if the editor has correct auto-indent, the cursor should be at the correct position, but the close-parens will stay on the previous line

(when pressing enter I mean)

Replete's example does work.

it’s the difference between [pressing enter in indent mode](http://shaunlebron.github.io/parinfer/#pressing-enter) and [the new paren mode cursor feature](http://shaunlebron.github.io/parinfer/#knowing-when-parens-move-in-paren-mode)

Ah, so what I'm trying to get is similar to vim's built in auto-indent, where it will match the indentation of the previous block of lisp.

Sorry about the confusion here 😛

vim isn't matching it though, because the parens aren't closed (it would if they were open).

yeah, I think you’re talking about cursor position

I would try it myself in neovim, but I somehow crashed my neovim

Yeah, cursor position, but from opening a new line underneath a closed block of lisp.

I have to head out right now, but I’ll read this later

In my head, it was supposed to move the cursor to match the previous indentation when doing that. No idea if this fits with parinfers development goals or not

@dominicm: If you insert a newline at the end of the form auto-indent puts you in the right place, but usually you just go to the end of a top level form, which puts you on a new top level indent. (basically I've had to get use to counting closing parens so i can insert in the right place.... It's slightly annoying)

@snoe I'm in the habit of just hitting "o" beneath a top level form, and expecting to be whoosed to the previous indentation. I'm currently just hitting space & typing until I get it right (or using % on the opening bracket)

yeah i've had to stop doing that 😕

Maybe it'll become a parinfer feature, who knows!