Closed Smattr closed 1 year ago
When you jump into a file that is already open somewhere else by Vim, you get the Vim lock file screen, and then if you abort this you get an assertion failure:
clink: clink/src/screen.c:200: screen_free: Assertion `active && "double screen_free() calls"' failed.
Presumably what's happening here is that any non-zero return code from Vim triggers this path.
When you jump into a file that is already open somewhere else by Vim, you get the Vim lock file screen, and then if you abort this you get an assertion failure:
Presumably what's happening here is that any non-zero return code from Vim triggers this path.