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 searching for an exact term in quotes, the vault search successfully filters down the notes it displays to only those that contain the exact search. However, the in-file search (whether selected to begin with or switched to from vault search) seems to behave exactly the same as if there are no quotes. Specifically, all tokens in the file that begin with any of the words included in the exact search match and are shown.
Here's an example screenshot:
And a screenshot of the associated logs:
Your environment:
Omnisearch version: 1.20.2
Obsidian version: 1.5.3
Operating system: Microsoft Windows 11 Home 10.0.22621 Build 22621
Number of indexed documents in your vault (approx.): 850
Things to try:
Does the problem occur when Omnisearch is the only active community plugin: Yes
Does the problem occur when you don't index PDFs, images, or other non-notes files: Yes
Does the problem occur after a cache reset: Yes
The text was updated successfully, but these errors were encountered:
sngchn85
changed the title
[BUG] Quotes around exact terms do not affect in-file search #335
[BUG] Quotes around exact terms do not affect in-file search
Jan 1, 2024
I'm on
Omnisearch version: 1.21.1
Obsidian version: 1.5.8
This bug still exists. For this reason, I often have to switch back to the native Obsidian search to find what I'm looking for. It would be nice if we didn't need to juggle.
Problem description:
When searching for an exact term in quotes, the vault search successfully filters down the notes it displays to only those that contain the exact search. However, the in-file search (whether selected to begin with or switched to from vault search) seems to behave exactly the same as if there are no quotes. Specifically, all tokens in the file that begin with any of the words included in the exact search match and are shown.
Here's an example screenshot:
And a screenshot of the associated logs:
Your environment:
Things to try:
The text was updated successfully, but these errors were encountered: