Closed andymass closed 3 years ago
Hey, I just remembered that there was this PR here. I finally returned to my own plugin and did some improvements. This included the usage of a column precise location. Reading up the PR description again it appears to solve the same issue. You might want to try if the latest version satisfy you? Did you had any other issues?
When jumping to declarations etc, include the column number in the target pattern. (Fixes #1)
_get_line_byte_from_position
to translate utf-16 position into column bytes, except that this function actually loads buffers unexpectedly. Instead, we usevim.str_byteindex
directly in combination with:%#c
to target the column byte.Considered alternatives:
lsp.util.jump_to_location
) which and only do the utf-16 to utf-8 conversion on the jump, which is potentially cheaper.