[BUG] I don't thnk indexing is actully happing

[the1gofer]

I keep getting the popup that says many files need to be indexed and that it may cause isues with obsidian wile that happens, and while I'm having the suttering, the number never seems to go down. Is there any way to see if indexing is actually happening, or is stalled?

[scambier]

When you created this bug, there was a template to fill that asked a few important questions, such as:

• Operating system:
• Number of indexed documents in your vault (approx.):
• Does the problem occur when Omnisearch is the only active community plugin:
• Does the problem occur when you don't index PDFs, images, or other non-notes files:

You should make sure that "Save index to cache" is enabled, if you're not on iOS. After that, restart Obsidian and let Omnisearch do the indexing. There will be another notification that will tell you "Your files have been indexed" once it's done. The Omnisearch modal will also display a message when you open it while indexing is still running.

It's important to let it run fully, otherwise the cache won't be written

[the1gofer]

thanks for the response. It seems like the indexing is done, (no stuttering), but the modal never says completed.

Jason Crews

On Sat, Apr 27, 2024 at 12:41 AM Simon Cambier @.***> wrote:

When you created this bug, there was a template to fill that asked a few important questions, such as:

• Operating system:
• Number of indexed documents in your vault (approx.):
• Does the problem occur when Omnisearch is the only active community plugin:
• Does the problem occur when you don't index PDFs, images, or other non-notes files:

You should make sure that "Save index to cache" is enabled, if you're not on iOS. After that, restart Obsidian and let Omnisearch do the indexing. There will be another notification that will tell you "Your files have been indexed" once it's done. The Omnisearch modal will also display a message when you open it while indexing is still running.

It's important to let it run fully, otherwise the cache won't be written

— Reply to this email directly, view it on GitHub https://bitli.pro/293e7_e058a4eb, or unsubscribe https://bitli.pro/293e8_530759c0. You are receiving this because you authored the thread.Message ID: @.***>