Open korbiniak opened 2 years ago
Do you usually use fzf-native
? Because it calculates the highlight positions (i can reproduce it with fzf-native
) But it would also be good if we check the internal sorters as well as fzy-native
I don't, I used it here because it was in the template for mre.
Also setting the selection_caret
to anything more than 2 chars causes the same problem. Here I set it to "> "
(2 ws):
Testing on fzf
itself I get:
$ find . | fzf --pointer=""
invalid character in pointer
And with more than 2 characters:
$ find . | fzf --pointer="> "
pointer display width should be up to 2
So, maybe not supported?
I suspect the issue is related to some weird byte indexing/encoding shenanigans in this call:
After some vim.inspect
ing of the parameters passed into that function everything seems fine up to that point. I tried playing with vim.str_byteindex(..)
but no luck.
Setting it to an empty string (selection_caret = ""
) also breaks highlight matching
Do you usually use
fzf-native
? Because it calculates the highlight positions (i can reproduce it withfzf-native
) But it would also be good if we check the internal sorters as well asfzy-native
I can reproduce it with zf-native
(natecraddock/telescope-zf-native.nvim)
Description
When setting up selection_caret for " " (U+F064) the search highlighting is broken.
Neovim version
Operating system and version
Linux 5.17.3-arch1-1
checkhealth telescope
Steps to reproduce
selection_caret
to the emoji " " (U+F064)Expected behavior
No response
Actual behavior
Broken search highlighting. As you can see, the "r/" is also highlighted. It is not if the carret is for example "> ".
Minimal config