word separators in searching #867
Comments
It appears that you would need to override As I've been playing with search the last few days, I'm thinking we may need to add some search related config settings. One for this issue (word separators) and one for language support (see #826). Possibly even one to disable search support altogether? |
I'm switching the milestone for this issue to 1.0 as this would be part of the search refactor which I'm working on for 1.0 (see my previous comment). |
In mkdocs.yml define seperator like this: plugins: - search: seperator: '[\\s\\-\\.]+' Fixes mkdocs#867.
In mkdocs.yml define seperator like this: plugins: - search: seperator: '[\\s\\-\\.]+' Fixes mkdocs#867.
In mkdocs.yml define seperator like this: plugins: - search: seperator: '[\\s\\-\\.]+' Fixes mkdocs#867.
In mkdocs.yml define seperator like this: plugins: - search: seperator: '[\\s\\-\\.]+' Fixes mkdocs#867.
* Use a web worker in the browser with a fallback (fixes #859 & closes #1396). * Optionally pre-build search index (fixes #859 & closes #1061). * Upgrade to lunr.js 2.x (fixes #1319). * Support search in languages other than English (fixes #826). * Allow the user to define the word separators (fixes #867). * Only run searches for queries of length > 2 (fixes #1127). * Remove dependency on require.js, mustache, etc. (fixes #1218). * Compress the search index (fixes #1128).
Suppose in the markdown file, I have a "word": "Foo.bar", the current search function is not able to pick "Foo.bar" if I search for "bar". May be some settings in lunr.js will do the job?
The text was updated successfully, but these errors were encountered: