Bug 154896

Summary:	read-only files: disallow editing
Product:	[Applications] kate	Reporter:	Maciej Pilichowski <bluedzins>
Component:	general	Assignee:	KWrite Developers <kwrite-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	wishlist
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Maciej Pilichowski 2007-12-31 13:30:22 UTC

Version:            (using KDE KDE 3.5.8)
Installed from:    SuSE RPMs

The current policy is: allow editing, disallow saving.
The wished policy is: disallow editing and saving.

Why? It is more natural to not being able to edit non-editable file, user should only view it.

If there is need of "alteration" of the file (impossible of course) user should save-as the file first and then edit the saved file.

The wished behaviour is similar to OOffice (for example, the current one to MC -- and while I didn't edit any system files with Kate, I did it with MC and this was all the time annoying (edit -> oh, I cannot save -> save as -> root -> copy).

So, if the file is read-only act in read-only mode as soon as possible.

Comment 1 FiNeX 2007-12-31 13:40:06 UTC

This happen to the new kate version.
Users should be informed that the file is in read-only mode.

Comment 2 Maciej Pilichowski 2007-12-31 13:46:45 UTC

This another issue, but you are right. Minor, related wish:
http://bugs.kde.org/show_bug.cgi?id=154897

about informing user.

Comment 3 Stefan Endrullis 2008-02-14 15:15:53 UTC

On the other side it would be great if kate (or whole kdelibs) would check file permissions when you save a file. If you are not able to overwrite the file, it should check, if the owner of the file is able to and then it would be nice to get a "run as user" dialog to enter username and password to save the file with the new rights.

Comment 4 Maciej Pilichowski 2008-02-14 19:04:01 UTC

I would rather opt for not having such feature -- I am rather afraid of mixing front-ends program with security (maybe it is paranoia :-) ). Besides, once introduced, it is potential risk of having bugs -- are you sure the privilege is used only for saving, or kept for further editing&writing, if yes, user can overwrite some important file by mistake too easily.

Comment 5 Dominik Haumann 2011-06-29 15:59:22 UTC


*** This bug has been marked as a duplicate of bug 105459 ***