Henry John Kupty comments

Results 131 comments of


                                            Henry John Kupty

Feature request: show stacktrace when eval produces an error

I added a workaround for this issue. The correct way to deal with it would be to implement persistent sessions so `*e` would work. Right now, I'm accumulating the errors...

Feature request: show stacktrace when eval produces an error

I'm implementing sessions finally, which allow us to implement an actual wrapper for errors since they now can belong to a session we control. I'll follow up on that once...

Feature request: show stacktrace when eval produces an error

Btw, just tested and, on #55, one can: ```viml :AcidEval (/ 0 0) :AcidEval *e :messages ``` To get full stacktrace of previous error

Feature request: show stacktrace when eval produces an error

Sessions were merged, so I can now proceed with a proper handling of errors/stacktraces.

scapegoat failOnError := false

I think this is related to #72 .

Bring back Max{Info,Warning,Error}s

Actually.. It was removed in b715bd1a8d6, the previous one just commented it out.

Bug: for classes generated by Retrofit spies fail in coVerification clause on suspend functions

This seems to be the same as #608 and #554, unless I'm missing something.

fix(core): `nvim_buf_set_extmark()` uses byte-index

Ok, this has kind of bit-rot and I guess it's my fault.. The recently merged #343 seems to touch upon some of this work. I'm out on vacations, but soon-ish...

Gradle and multi-projects

Sorry for bumping an old thread but it doesn't seem to work for kotlin. After checking #496, it does seem to only implement the feature for java.

java.lang.OutOfMemoryError: Java heap space

I just want to mention I'm experiencing the same issue using kotlin-language-server from neovim. From my preliminary tests, it seems to be caused by a huge allocation in the `debounce0`...