View Single Post
Old 12-21-2022, 02:34 PM   #4
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 79,798
Karma: 146391129
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by falsifier View Post
I've been using linux version of Calibre's ebook editor for years, since version 3.x I think. I really like it, all the progress it made, but there's this one thing I can't (under)stand: when saving, it silently overwrites read-only ebook files. The read-only attribute is there for a purpose you know, you should at least get a warning about the file being write-protected and a chance to back off…

Last time it worked well enough was in version 5.36 -- when you clicked 'save' you got an error message that the file could not be saved, so you knew you might had done something you didn't want to do. Since 5.37 there's no more message and the file just gets silently overwritten despite being protected -- in theory -- by its read-only attribute. I thought that maybe this was just a new bug and would be fixed soon but there were already more than 10 releases since 5.36 and it still does that. I tried to be careful about it but since I frequently have several editor windows open I've already got bitten by it several times -- I modified and saved wrong ebook files effectively losing large parts of them.

So, am I the only one who finds overwriting of read-only files without any warning unacceptable? Is this a “feature” of this editor or indeed a bug?
It's the fault of Linux for being buggered. Windows would not allow me to overwrite if the file was read-only.
JSWolf is offline   Reply With Quote