https://bugs.documentfoundation.org/show_bug.cgi?id=160466
--- Comment #9 from ady <[email protected]> --- (In reply to Heiko Tietze from comment #8) > The command line parameter /r has no effect for me The specific command is only an anecdote. For this request, the way the file is set to read/only is not relevant. > > Maybe you can change your script and set the attribute before starting > LibreOffice, and when done you remove the r/o flag. Why the OP would be interested in removing the r/o flag? That is exactly what the OP does not want to do, ever for this file. In my system, LO is _not_ behaving like Excel. IIRC, Excel allows edition but warns about saving when it is working in r/o mode (and please correct me if I am remembering incorrectly). LO does not allow edition in r/o mode. STR: 1. New Calc workbook. 2. Save with some name. 3. Menu Edit > "Edit Mode" (not to be confused with "Cell Edit Mode"). 3.1. Note that, in the upper title bar, Calc added "(read-only)" to the name of the file. 4. Attempt inserting some value in some cell; you might try, but no edition is actually allowed. Actual result: Under this Mode, the file cannot be edited. So, blocking _Edit_ and blocking _Save_ are ATM one and the same status. Request: Have two separate statuses, in which you are still allowed to Edit (as long as Protection also allows it), even when you are not allowed to Save (with the same "path/name.type" file). "Save As" a different "path/name.type" is allowed. When blocking the possibility to Save (i.e. r/o mode), and the user anyway attempts to save the editions that were made (the latter being something that is currently not possible to do), the result could be to suggest saving as a different (path/name.type) file. IOW, allow to Edit (always according to Protection rules already established in the specific file) even when the file is set to r/o. Use-case: I want to always open the very latest version of a file that is always in a permanent edition/update status by some colleague, and perform some editions that are relevant for me but not for others (e.g. What-If, Solver...), but I never want to overwrite my edition onto the original file I opened. I want to be able to perform changes and read the results, but I never want to overwrite the original file. IOW, the file works similarly to a template (which happens to be in some "continuous" update by someone else), never to be overwritten by me. The current alternative is to open the file as r/o, then first of all save as a different file, allow Edit Mode and perform editions. Once I finish my work with the new file (that do not need to be saved), close it and delete the file. When I need the procedure again, repeat the alternative whole procedure, saving a new file each time, which I have to delete every time. Hopefully this clarifies the focus of the request. -- You are receiving this mail because: You are the assignee for the bug.
