Zim

Shared dropbox data corrupted index on one PC

Asked by Benjamin P Trahan

Using Dropbox to share zim (0.62) data between two netbooks running Manjaro 16.06.1, moved and renamed a bunch of pages on one, Index did not update correctly on the other. Tools, Update index has no effect.
Tried the terminal minus option (I assume that is a minus sign in "zim -index") that got various errors, last of which was zim data not found.
I would like to know a little more about the relationship between the apparent local index and the shared data before I try pointing the second PC at the dropbox data. I don't want to mess up the data for the PC that is OK. Also, I am not sure how to specify the location of the data on the zim -index terminal command.
The index and data appear to me good on the PC that made the changes, so I am just trying to make sure my only access to the data does not have a problem introduced to it.

Question information

Language:
English Edit question
Status:
Answered
For:
Zim Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Jaap Karssenberg (jaap.karssenberg) said : 		#1

I believe more recent versions of zim 0.65 or 0.66 are more robust for this
case.

Regards,

Jaap

On Mon, May 1, 2017 at 6:27 AM Benjamin P Trahan <
<email address hidden>> wrote:

> Question #630469 on Zim changed:
> https://answers.launchpad.net/zim/+question/630469
>
> Description changed to:
> Using Dropbox to share zim (0.62) data between two netbooks running
> Manjaro 16.06.1, moved and renamed a bunch of pages on one, Index did not
> update correctly on the other. Tools, Update index has no effect.
> Tried the terminal minus option (I assume that is a minus sign in "zim
> -index") that got various errors, last of which was zim data not found.
> I would like to know a little more about the relationship between the
> apparent local index and the shared data before I try pointing the second
> PC at the dropbox data. I don't want to mess up the data for the PC that is
> OK. Also, I am not sure how to specify the location of the data on the zim
> -index terminal command.
> The index and data appear to me good on the PC that made the changes, so I
> am just trying to make sure my only access to the data does not have a
> problem introduced to it.
>
> --
> You received this question notification because you are an answer
> contact for Zim.
>

Revision history for this message
Benjamin P Trahan (bentrahan) said : 		#2

Sorry. I was a bit remiss in reporting versions. Good zim index is on a 32 bit Acer one notebook running Manjaro 16.10 and zim 0.65; Bad index is on a 64 bit acer one notebook running Manjaro 16.06.1 and zim 0.65.

Revision history for this message
Benjamin P Trahan (bentrahan) said : 		#3

I repeat, initial report of zim 0.62 was an error. Both machines are, and have been for a long time, at zim 0.65.

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

In that case make sure you have the "shared" option enabled in the notebook
properties.

Running "zim --index -V path/to/notebook" should force a full re-build of
the index (that is 2 x "-" before "index", 1 x "-" before "V")

-- Jaap

On Tue, May 2, 2017 at 4:57 AM Benjamin P Trahan <
<email address hidden>> wrote:

> Question #630469 on Zim changed:
> https://answers.launchpad.net/zim/+question/630469
>
> Benjamin P Trahan gave more information on the question:
> I repeat, initial report of zim 0.62 was an error. Both machines are,
> and have been for a long time, at zim 0.65.
>
> --
> You received this question notification because you are an answer
> contact for Zim.
>

Can you help with this problem?

Provide an answer of your own, or ask Benjamin P Trahan for more information if necessary.

To post a message you must log in.