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
When the search index is built, the text is split into words. This is done with the regex \w+ - line 85. \w includes characters, but also includes underscores and should not.
The consequence is that if your text has word1_word2_word3 then doing a search for word2 or word3 will not find that match. Underscore seperated words are common in Python and elsewhere, and the Javascript tokenizer does consider underscore as a splitter.
I experienced this with SQLITE_CONFIG_URI being in my doc, but searches for uri do not find it.
How to Reproduce
You can see this with Sphinx's own doc. Search for apply_source_workaround and you'll see apply_source_workaround found. Now search for workaround and apply_source_workaround is not found at all.
Describe the bug
When the search index is built, the text is split into words. This is done with the regex
\w+
- line 85.\w
includes characters, but also includes underscores and should not.The consequence is that if your text has
word1_word2_word3
then doing a search forword2
orword3
will not find that match. Underscore seperated words are common in Python and elsewhere, and the Javascript tokenizer does consider underscore as a splitter.I experienced this with
SQLITE_CONFIG_URI
being in my doc, but searches foruri
do not find it.How to Reproduce
You can see this with Sphinx's own doc. Search for apply_source_workaround and you'll see
apply_source_workaround
found. Now search for workaround andapply_source_workaround
is not found at all.Environment Information
Sphinx extensions
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: