You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not really a huge issues, just something nice to have:
Sometimes incorrect coordinates (row/col) can lead to segmentation fault (noticed during work on an lsp client). This is unlikely to happen in well-behaved clients, but it might happen, so ideally the off by one errors in indexing would be caught rather than leading to a segfault.
Not really a huge issues, just something nice to have:
Sometimes incorrect coordinates (row/col) can lead to segmentation fault (noticed during work on an lsp client). This is unlikely to happen in well-behaved clients, but it might happen, so ideally the off by one errors in indexing would be caught rather than leading to a segfault.
I think this is due to a complete request with col = 6 instead of col = 5 (edited):
The text was updated successfully, but these errors were encountered: