This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (25)
- # beginners (132)
- # boot (89)
- # cider (26)
- # clara (12)
- # cljs-dev (10)
- # cljsrn (11)
- # clojure (151)
- # clojure-germany (8)
- # clojure-russia (1)
- # clojurescript (137)
- # cursive (33)
- # datavis (28)
- # datomic (3)
- # devcards (8)
- # hoplon (5)
- # immutant (11)
- # jobs (4)
- # ldnclj (58)
- # lein-figwheel (7)
- # off-topic (95)
- # om (114)
- # onyx (91)
- # parinfer (38)
- # portland-or (1)
- # re-frame (26)
- # reagent (1)
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
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)
if you could create a concrete case for what you’re expecting (current text -> keystroke -> expected output), I can better understand
@shaunlebron: I'm not sure nvim-parinfer.js supports anything outside indent mode anyway.
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
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.
vim isn't matching it though, because the parens aren't closed (it would if they were open).
Yeah, cursor position, but from opening a new line underneath a closed block of lisp.
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)