View Single Post
Old 12-21-2022, 03:08 PM   #5
lomkiri
Groupie
lomkiri ought to be getting tired of karma fortunes by now.lomkiri ought to be getting tired of karma fortunes by now.lomkiri ought to be getting tired of karma fortunes by now.lomkiri ought to be getting tired of karma fortunes by now.lomkiri ought to be getting tired of karma fortunes by now.lomkiri ought to be getting tired of karma fortunes by now.lomkiri ought to be getting tired of karma fortunes by now.lomkiri ought to be getting tired of karma fortunes by now.lomkiri ought to be getting tired of karma fortunes by now.lomkiri ought to be getting tired of karma fortunes by now.lomkiri ought to be getting tired of karma fortunes by now.
 
lomkiri's Avatar
 
Posts: 170
Karma: 1497966
Join Date: Jul 2021
Device: N/A
Quote:
Originally Posted by kovidgoyal View Post
And it was introduced precisely to prevent someone from losing hours of work if they happen to edit a file that was readonly for a random reason and they dont know how to fix file permissions (which is surprisingly common).
I am the author of this request, but in fact, my concern was with "save-as", not "save". I agree with Falsifier that it shouldn't be possible to overwrite a RO file, not without warning, at least, but my problem was that it wasn't possible to "save as" to a new file either, which would be the expected behavior. So I've lost my work on that epub. The change you've made at that time solved this issue, but a side-effect was that RO files were not protected anymore (I've noticed it at that time, but said nothing, I didn't want to bother you).

I don't know if I understand the code of your present patch correctly, but it seems that you've put a warning, but no option to desist. Am I right ? If it's the case, I think it would be welcome to be able to desist, and to "save as" instead.

Last edited by lomkiri; 12-21-2022 at 03:11 PM.
lomkiri is offline   Reply With Quote