Version: (using KDE KDE 3.5.8) ...for example text "read-only" in the titlebar. ...for example text "read-only" in the titlebar.
Well, I think it's a very valid wish, but still a wish, not a bug. Note that implementing this would likely obsolete bug #38167.
Thomas, sorry, of course this is a wish. Thank you for pointing out that report.
Different possible visual indicators: 1) Reduced contrast between the background and the text colour 2) A specific font 3) Cursor has a small X next to it 4) Mouse cursor has a small X next to it when mousing over the text 5) Cursor could be of the large highlight-one-letter variety (like the C64 had) 6) OMG Ponies Pink theme used when opening read-only files.
Even more important since we have swap file recovery. There indeed should be a visual indication, change to bug instead of wish.
*** Bug 232671 has been marked as a duplicate of this bug. ***
Git commit e5a6f98c649e4fe4cc01af55ad925b7b7b643517 by Joseph Wenninger. Committed on 24/10/2012 at 16:23. Pushed by jowenn into branch 'master'. KATE & KWrite show [read only] in the caption if a document is set read only. Perhaps kdevelop should do the same. The KTextEditor::Document has a new signal readWriteChanged(Document) which is emitted if the state changes. It should be used together with the related KParts functions M +6 -1 kate/app/katemainwindow.cpp M +5 -0 ktexteditor/document.h M +7 -2 kwrite/kwritemain.cpp M +1 -0 part/document/katedocument.cpp M +2 -1 part/document/katedocument.h http://commits.kde.org/kate/e5a6f98c649e4fe4cc01af55ad925b7b7b643517
I just tested this with kate and kwrite built from kf5 sources - this feature seems to have regressed and is not working anymore.
@Milian: You need to set the document read-only *yourself*. Then the visual indicator is there. What does not work is that read-only files from the FS are automatically marked as read-only in the Kate document (bad).
We never had that for "read-only" files on disk, only for "you made the file read-only". There is a wish for visual indication, thought. *** This bug has been marked as a duplicate of bug 366727 ***