parinfer

shaunlebron 2018-08-20T21:20:41.000100Z

the indentation suggestion is from codemirror, not parinfer

shaunlebron 2018-08-20T21:21:41.000100Z

parinfer accepts different indentation prefs from the editor (2-space vs first arg aligning)

shaunlebron 2018-08-20T21:23:01.000100Z

(bar   1 
     2)

shaunlebron 2018-08-20T21:23:40.000200Z

I can see the desire to have parinfer correct this state

shaunlebron 2018-08-20T21:24:51.000100Z

parinfer only knows how to preserve indentation relative to the position of its parent open-paren

shaunlebron 2018-08-20T21:26:50.000100Z

I’ve been tracking this request as “indentation stickiness”

shaunlebron 2018-08-20T21:26:52.000100Z

https://github.com/shaunlebron/parinfer/issues/151

shaunlebron 2018-08-20T21:30:24.000100Z

I called it “sticky” because of the behavior this would cause in the case: 1.

(foo bar
   baz)
2. delete foo:
(| bar
   baz)
3. type “something”:
(something| bar
            baz)

shaunlebron 2018-08-20T21:35:45.000100Z

my point is—the user originally had two space indentation, but will end up with first-arg aligned indentation if parinfer tries to involve itself with indentation preferences not related to structure