-
-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
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
[BUG] Sometimes previously typed search phrase is not selected on opening Omnisearch again #105
Comments
I'm having the same problem - would appreciate a fix. Thanks. |
Me too - could we have a setting to clear previous searches upon close/open of Omni? |
One more idea: if fixing phrase not always selecting on Omnisearch open happen to be difficult, maybe a simpler temporary workaround would be to have settings option to always open Omnisearch with an empty input 🤔 |
I'll take a look at this issue asap, probably once PDF indexing is shipped. |
I have noticed that if I use the keyboard to navigate to a search result, then the search term is saved as expected. However, if I use the mouse to go to the note, the search term is not saved. |
Am not sure whether to consider it a bug or a feature request, but since it seems Omnisearch behaves in an inconsistent manner on an edge case, I think it's more like a bug:
Problem description:
Usually when I open Omnisearch, the previously typed search phrase is there, already selected, so whatever I type will replace the old one. But sometimes the cursors is at the end of the previous phrase, making me unconsciously type after it, resulting with a search phrase being a concatenation of the old and the new one.
I managed to reproduce it in a quite deterministic manner, but there are still situations where I am not sure about its determinism.
What I try to do to reproduce the issues:
BTW I stuck upon this issue a lot when I switch between windows, but was unable to reproduce it in a kinda deterministic way, while the steps with copy-paste worked for me.
Just in case, this is my setup regarding editing modes, but please be aware I was able to reproduce the issue in both "Source mode" (the one I use) and the "Live Preview" mode
Your environment:
app.vault.getFiles()
yields13632
for meThe text was updated successfully, but these errors were encountered: