@cfleming: Hi, I found another defect with parinfer in cursive: 1.2.1. Just wanted to drop a note in case you are working on it anyway.

@sveri: Thanks, much appreciated. I’ll have to try that, but that look like a bug in parinfer proper, not Cursive. I’ll check on Monday.

@cfleming: Totally forgot the link to the issue: https://github.com/cursive-ide/cursive/issues/1342 Just saw that there are even more bugs with parinfer. Reminds me how hard development is and how impossible to test every case.

@sveri: Yeah, although parinfer is especially bad - it’s been very difficult to integrate properly.

The bugs are like whack-a-mole

@sveri: I just confirmed your issue is a bug in parinfer itself: https://github.com/shaunlebron/parinfer/issues/109

@cfleming: Thanks for looking at it, I have not of the possibility that it could be in parinfer itself.