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
Example file with many sorts of occurrences of missing highlights when searching for "q":
voidreproduce()
{
// A semantic token gets a very faint highlight when searching.auto qqqq = "qqqqqqqq";
// Error markings are drawn nicely.auto qqqqq qqqqqq;
// Even-numbered rows.int qqqqqq;
int qqqqqqq;
// Odd-numbered rows. On some font sizes, the tops and bottoms are gone.int qqqqqqqq;
int qqqqqqqqq;
int i_hide_highlights_under_my_background;
int qqqqqqqqqq;
int i_hide_them_too;
// qqqqqqqqqqqqq Comment highlights don't bother each other.// qqqqqqqqqqqqq But semantic tokens do bother comments.int qqqqqqqqqqq;
// qqqqqqqqqqqqq// Highlight for selected text works.auto qq = 1;
qq = 2;
qq = 3;
qq = 4;
}
Expected behavior
Search hits are highlighted very visibly, with surrounding, unbroken rounded rectangles, as shown in the image below.
In this screenshot, LSP's semantic highlighting is disabled.
Screenshots
Search highlights are buggy.
Highlights for selected text occurrences work fine.
The bug doesn't seem to depend on the theme used. Monokai and others suffer from it too.
With display scale 100%, the partial highlights disappear completely. Font size 48 is used to bring up details.
Environment
OS: Windows 11 version 23H2 (OS Build 22631.3593)
Display scale 150%
Sublime Text version: 4180
LSP version: 2.2.0
Language servers used: Clangd 18.1.8, used through LSP-clangd 1.7.0
Thanks for the near-instant reply and for linking those resources. I'm not familiar with this project, so while searching with highlight-related terms, I didn't manage to find that list of upstream issues. This surely does seem to be one those.
I've tried to fix it via SessionView.initialize_region_keys, but it does not work; apparently the find region key (https://forum.sublimetext.com/t/what-is-the-find-results-highlight-key/69032/4) is automatically initialized by ST as soon as a new view is created. We would need to initialize the semantic highlighting keys before that happens, so I don't think this can be fixed on the LSP side.
Describe the bug
When semantic highlighting is used, ST's search highlight is mostly hidden for hits within semantic tokens.
To Reproduce
Steps to reproduce the behavior:
LSP.sublime-settings:
The color for
highlight
is set so that hard-to-see highlights stand out better.Mariana.sublime-color-scheme:
Example file with many sorts of occurrences of missing highlights when searching for "q":
Expected behavior
Search hits are highlighted very visibly, with surrounding, unbroken rounded rectangles, as shown in the image below.
In this screenshot, LSP's semantic highlighting is disabled.
Screenshots
Search highlights are buggy.
Highlights for selected text occurrences work fine.
The bug doesn't seem to depend on the theme used. Monokai and others suffer from it too.
With display scale 100%, the partial highlights disappear completely. Font size 48 is used to bring up details.
Environment
Additional context
This is likely related to #1934.
The text was updated successfully, but these errors were encountered: