[feature] difference of repos after force resync of remote, about nixnote2

[robert7]

If fixed the problem with command line.
So the sync from command line now works for me (syntax: nixnote21 sync).
The version with --syncAndExit still crashes; i did n't even knew, there are 2 different ways how to start sync (I'll look at it later).

If think the requested feature is not realistic to implement => won'tFix :)

But the sync should already be quite stable.

1. "corrupted my remote evernote repo" - Evernote does a quite strong validation - this should be VERY unlikely - this should NOT happen ever
2. "have not lost data" - if the note isn't shown't as "dirty", then you can be quite sure, that your changes landed in cloud (where they should be safe, whatever is on your localhost)
3. "nixnote-broken" this should not happen anyway!! :) ... except you do e.g. wild tag refactoring on remote side like in #10 (=> don't do that)

The fix in command line is in "beta-3a" - temporarily you can find it at https://www.dropbox.com/sh/bropykm64u8zdmv/AABmCL47YtUXglFMRnTFNnfia?dl=0

[robert7]

I removed --syncAndExit in beta-3b as it was redundant.

[robert7]

I'm closing this; as the problem sync from command line is fixed; and the diff is not realistic to implement (and should not be needed).