Quote:
Originally Posted by DiapDealer
Then how about this? As soon as Sigil 0.8.2 stops working, make a backup of the existing sigil.ini file. Start Sigil 0.6.2 and close it, to "fix" the ini file, and then diff the "fixed" version of the ini file against the backed up "broken" ini file.
|
Yeah, I tried that.
Many, many lines of encoded gobbledygook.
\x62\0r\0o\0w\0s\0\x65\0r\x1\0\0\0X\0\0\x2\xd1\0\0 \0S\0\xff\xff\xff\xfb\0\0\0\x16\0\x63\0l\0i\0p\0s\ 0w\0i\0n\0\x64\0o\0w\0\0\0\
etc, etc.
Quote:
Originally Posted by DiapDealer
I have no answer for that question. Mostly because I don't care why it keeps its own copy of the clipboard ... any more than you care to explain why you want to keep using XP on new hardware.  |
Large blocks of irrelevant text complicates file compare, for one thing.
"Resync Failed. Files are too different."
Anyway, next time Sigil chokes I will see if just replacing the ini file with a "known good" version works.
(Rather than deleting it, which would lose all my preferences).