Presence of a single- or double-byte unicode symbol should not affect correctness of code highlighting.
Following screenshot demonstrates correct behavior. fmt is a Go module identifier and is not preceded with an unicode symbol on particular row :
What happened instead?
Identifier highlight starts off the actual identifier position.
Following screenshot demonstrates the issue. lib is also a Go module identifier but now it is preceded with an unicode symbol, in a first string argument of Println function.
In the first case("bubble sort") the symbol is ⇒ (0x21d2), two-byte char so highlighting starts off by two columns.
In the second case("selection sort") the symbol is á (0xe1), single-byte char so highlighting starts off by one column.
What did you expect to happen?
Presence of a single- or double-byte unicode symbol should not affect correctness of code highlighting.
Following screenshot demonstrates correct behavior.
fmtis a Go module identifier and is not preceded with an unicode symbol on particular row :What happened instead?
Identifier highlight starts off the actual identifier position.
Following screenshot demonstrates the issue.
libis also a Go module identifier but now it is preceded with an unicode symbol, in a first string argument ofPrintlnfunction.In the first case("bubble sort") the symbol is
⇒(0x21d2), two-byte char so highlighting starts off by two columns. In the second case("selection sort") the symbol isá(0xe1), single-byte char so highlighting starts off by one column.Configuration (MUST fill this out):
Vim 9.0.1882, Linux x86_64
vim-go version:
current