Yes, trying to saving to a location where you have no permissions can cause problems on some platforms and instead of a nice -1 return value they throw an exception and some even abort. On those platforms, Sigil tries to catch any exceptions and catch abort signals and try to "save the day" and not close. Sometimes that works and Sigil can resume and other times it can not. So that message is a bit Windows-like and misleading as well. I will try to change that error message and see if there are better ways to handle permission violations on write that will work across platforms or better yet detect them without an actual write-attempt.
KevinH
|