Sigil works just fine with Adding Files that are set to read-only in directories with execute permission that the user owns. I just tested this on macOS and Linux. No crashes. I do not have a Windows box to test with that but I would guess it works there as well. I think the act of changing files to be read-only either changed owner or changed the folder's permissions which explains why Sigils epub save-as could not write to that folder.
So this is either a Window's specific thing or Windows permissions on the folder enclosing the the read-only file are incorrect on your machine.
Glad to hear you figured out what was wrong with your permissions. This is not a bug in Sigil at least on Linux and MacOS.
@DiapDealer when you get a free moment would you please test using AddExisting on a file that the user owns that is set to read-only on your Windows build to determine if there is any Sigil issue at all on Windows?
Quote:
Originally Posted by Domenick
I apologize. Setting important files to read-only ensures I do not change them without creating a new version, thereby invalidating existing dependencies.
It was my standard novel CSS file which had not changed in years. It did not occur to me to check if the file was read-only, which begs the question, why would a read-only CSS file cause this behavior? Sigil could still read it, and Sigil had no reason to alter or write over the file.
Again, thank you.
|