index.db needs to be regenerated after svn update / git pull

[Josef Dalcolmo]

When sharing a notebook with others via VCS (for example SVN or Git), it is not recommended to share the .zim folder (as this contains local information). However, since the pages obviously can be changed after an 'svn update' or 'git pull', the .zim/index.db will be stale. Trying to run 'update index' won't do, because zim does not realize the pages have changed, nor does it know which pages have changed. Currently my workaround is to leave zim, delete the file .zim/index.db and start zim again. This will re-create the index.db but obviously that may take some time on a large wiki.

It would be nice to have support for this index.db re-creation from within Zim.

[Josef Dalcolmo (josef-dalcolmo)]

It seems like Zim deals well with new pages added outside of Zim, but does not handle well the disappearing of pages, even when manually running "Update Index".

[Jaap Karssenberg (jaap.karssenberg)]

The menu item "update index" is specifically intended for this purpose. Also on start zim re-scans the folder automatically.

Cannot reproduce issue, but next release will have redesign of indexing code

[Launchpad Janitor (janitor)]

[Expired for Zim because there has been no activity for 60 days.]