We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This not an issue but an enhancement that would improve the user experience.
Currently word highlight is key-sensitive. Please note in the example below 'text' is highlighted but not 'Text'
### Expected behavior: highlight both 'text' and 'Text'
I was searching over but couldn't find any specific to this enhancement. This could be done with a package setting i.e:
"highlight_key_sensitive" : false
### My environment: Sublime Text version: 4143 MacOS ventura 13.2.1
### Word Highlight.sublime-settings { "draw_outlined" : true, "mark_occurrences_on_gutter" : true, "highlight_when_selection_is_empty" : false, "highlight_word_under_cursor_when_selection_is_empty" : true, }
The text was updated successfully, but these errors were encountered:
there is
"case_sensitive": false,
in the settings which for me works and does exactly what you're looking for.
Sorry, something went wrong.
No branches or pull requests
This not an issue but an enhancement that would improve the user experience.
Currently word highlight is key-sensitive. Please note in the example below 'text' is highlighted but not 'Text'
### Expected behavior:
highlight both 'text' and 'Text'
I was searching over but couldn't find any specific to this enhancement.
This could be done with a package setting i.e:
"highlight_key_sensitive" : false
### My environment:
Sublime Text version: 4143
MacOS ventura 13.2.1
### Word Highlight.sublime-settings
{
"draw_outlined" : true,
"mark_occurrences_on_gutter" : true,
"highlight_when_selection_is_empty" : false,
"highlight_word_under_cursor_when_selection_is_empty" : true,
}
The text was updated successfully, but these errors were encountered: