Zim

Topics cloning 'ghosts' upon moving Win-7 to Linux

Asked by Pete

Hi Zim people!

   I been a raving Zim fan for years, simply nothing else comes close.
Anyway, I'm checking out Kubuntu linux (Saucy) as a windows-7 alternative.
I like tux indeed so far. But my Zims now exhibit an odd cloning for certain links,
it seems like just on those I'd made case-specific in WIndows.
The result is, now seeing some 'ghost files' alongside my same old usual entries.
The 'ghosts' are all empty, with the same titles, re-run as lower case.
E.g. 'ProJ' >> 'proj'.

So I re-named all 'ProJ' to 'PRJ', & let it re-index.
The proj still remained. ....So I
1st went through checking for back-links (from the bottom right), thinking I had some leftovers.
then 2) checked out the raw text files for the alleged link.
However, all such links in the text files seemed successfully re-named as 'PRJ'.
3) I tried taking out all the backup files named "xxxx.txt.bak", no change.
Generally Im careful to keep all my links 'absolute', i.e.
linking back to the uppermost parent page. (e.g. "proj:topic:subtopic" )
   Been re-indexing like crazy, these ghosts are still after me.

Seems by vsn. 55, you guys had
"* Fixed behavior of case-sensitive rename on a case-insensitive file system (windows)"
Saw one guy this Jan., asked about this behavior in moving TO windows, ...may have had
non-ascii characters when using different file system encodings...
https://lists.launchpad.net/zim-wiki/msg02158.html
  I dunno... in linux, I kept these ZIMs on an NTFS partition for a while, then moved them to an Ext4.
Then again, maybe it's my big ZIm: 374 files in 87 subfolders ~ OMG!

Thanks & CHeers! ~ Peter

Question information

Language:
English Edit question
Status:
Solved
For:
Zim Edit question
Assignee:
No assignee Edit question
Solved by:
Pete
Solved:
Last query:
Last reply:
Revision history for this message
Pete (oddbooks) said : 		#1

Ahem, think I answered me own Q.
Apparently in the (ordinarily) hidden .zim directory,
you can simply delete the 2 'hidden' files: state.conf & index.db.
Not only no harm done (I think),
  but clears up the problems I had above.
No more ghosts.
   Also, I wanted to change my 'calendar' files to 'Journal', to match the new plugin name.
Using Regexxer, I audited all my zim text files for 'calendar' in links, changing those to 'Journal'.
Then I deleted the state.conf & index.db's for those wikis, & opened my Zims refreshed.

Thx , Pete ; > )

Revision history for this message
Jaap Karssenberg (jaap.karssenberg) said : 		#2

Yep - deleting those files is a more extreme version of re-indexing. No
harm done, it is just a cache.

The same can be achieved by running "zim --index" from the commandline.

Regards,

Jaap

On Fri, Nov 1, 2013 at 8:36 PM, Pete
<email address hidden>wrote:

> Question #238450 on Zim changed:
> https://answers.launchpad.net/zim/+question/238450
>
> Status: Open => Solved
>
> Pete confirmed that the question is solved:
> Ahem, think I answered me own Q.
> Apparently in the (ordinarily) hidden .zim directory,
> you can simply delete the 2 'hidden' files: state.conf & index.db.
> Not only no harm done (I think),
> but clears up the problems I had above.
> No more ghosts.
> Also, I wanted to change my 'calendar' files to 'Journal', to match the
> new plugin name.
> Using Regexxer, I audited all my zim text files for 'calendar' in links,
> changing those to 'Journal'.
> Then I deleted the state.conf & index.db's for those wikis, & opened my
> Zims refreshed.
>
> Thx , Pete ; > )
>
> --
> You received this question notification because you are an answer
> contact for Zim.
>