parinfer

shaunlebron 2018-01-13T00:35:13.000247Z

i got markdown test cases for all the known bugs. gonna sleep on this and cut a release tomorrow: https://github.com/shaunlebron/parinfer/pull/181

shaunlebron 2018-01-13T00:38:07.000171Z

I know there’s more behavior to fix, but I’d like to get the bug fixes rolled out and close out all those issues. will start fresh on the new behavior problems when found

cfleming 2018-01-13T06:52:11.000034Z

@shaunlebron Sure, I have some cases noted down but haven’t had time to work up issues, sorry - I will do next week.

shaunlebron 2018-01-13T08:17:28.000039Z

@cfleming np, thanks for the previous issues. super helpful

martinklepsch 2018-01-13T11:44:45.000054Z

@shaunlebron parlinter looks pretty useful for editors that don’t support proper Lisp indentation

martinklepsch 2018-01-13T11:45:07.000066Z

that said I find the name slightly confusing as usually the name linter is associated with some form of static analysis (maybe just me?)

dominicm 2018-01-13T17:39:14.000152Z

@cfleming did you ever open source your parinfer implementation? I'm interested in seeing how well a JVM version of parinfer would integrate into neovim.

shaunlebron 2018-01-13T19:38:50.000034Z

@martinklepsch yeah I was afraid that would come up 😕

martinklepsch 2018-01-13T19:39:36.000083Z

Why not use the js version

shaunlebron 2018-01-13T19:39:45.000091Z

it was my experience at work using ESLint for javascript that it would catch a bunch of things, including formatting convention violations

dominicm 2018-01-13T20:17:58.000110Z

The neovim js api is very ES6 and hard to wrap from cljs

dominicm 2018-01-13T20:18:11.000025Z

But that's what is done now :)