[kate] [Bug 105459] [PATCH] switch to Read Only Mode for files that are read only
https://bugs.kde.org/show_bug.cgi?id=105459 Roc Vallès changed: What|Removed |Added Resolution|INTENTIONAL |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED CC||valles...@gmail.com --- Comment #6 from Roc Vallès --- This annoyed me today (17 years later). If it can't just be the default, please at least consider making it a setting. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 105459] [PATCH] switch to Read Only Mode for files that are read only
https://bugs.kde.org/show_bug.cgi?id=105459 Roc Vallès changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INTENTIONAL |--- --- Comment #9 from Roc Vallès --- > The argument that you realize some time later that the file is read only is > not true. The work is not lost, you can still save it in many ways including > copy pasting and save as etc. The patch does something unnecessary (loud warning about read-only). This is not what is being asked for. The important part of the patch is the part that enables read-only mode for read-only files. It is a matter of correct behavior. If the file is read-only, then the editor opens it in read-only mode, and this can be overridden as needed. Dealing with read-only headers and read-only documentation gets very tiring as they get unintentionally edited simply because the editor refuses to honor read-only file permissions. We already have a read-only mode. Editing a read-only file in the fixed scenario, where read-only mode gets auto-enabled, would be as easy as disabling read-only mode. And we would still be able to save these files, the same way we already do. It is not by chance this bug has so many duplicates: This is the expected behavior. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 105459] [PATCH] switch to Read Only Mode for files that are read only
https://bugs.kde.org/show_bug.cgi?id=105459 --- Comment #11 from Roc Vallès --- > Without any hint, it will even be more confusing. > Why shall I not write into that buffer? All I am reading is that adding such a hint would resolve any possible confusion. Which is, in any event, a separate issue. Read-only mode does already exist, so this issue does already exist. It would just become more prominent as we'd see read-only mode enabled more often. That's about it from me; Annoying as this issue is, it is not a hill worth dying on. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 436109] New: Distracting mouse pointer icon on top of linenumbers/folds columns
https://bugs.kde.org/show_bug.cgi?id=436109 Bug ID: 436109 Summary: Distracting mouse pointer icon on top of linenumbers/folds columns Product: kate Version: 21.04.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: valles...@gmail.com Target Milestone: --- Created attachment 137850 --> https://bugs.kde.org/attachment.cgi?id=137850&action=edit distracting non-disable-able icons that look like mouse pointers As of upgrading to 21.04.0 today, I've found working with kate (which I have been using everyday for a long time) extremely irritating, and really hard to work with. The source of this irritation is a new superfluous UI element. Some new icons I'm not sure about the function of (they don't seem clickable) that do look like mouse pointers --and thus are extremely distracting, as it seems as if the mouse pointer is there, twice-- are now present on top of the line numbers and folds columns. Attached screenshot highlights the issue. I haven't been able to find an easy way (other than reverting to previous package) to disable these. Please remove these or otherwise provide a way to disable showing them. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 436109] Distracting mouse pointer icon on top of linenumbers/folds columns
https://bugs.kde.org/show_bug.cgi?id=436109 --- Comment #2 from Roc Vallès --- Switching theme from breeze dark to breeze and then back to breeze dark fixed this. They're look like < > characters now, and behave as described. It must have been some bad handling of upgrade situation with some old version's services still running. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 372408] Option to omit shadow and transparent border from windows in Active Window and Window Under Cursor modes
https://bugs.kde.org/show_bug.cgi?id=372408 Roc Vallès changed: What|Removed |Added CC||valles...@gmail.com --- Comment #10 from Roc Vallès --- I'm seeing this issue while running spectacle with i3 as window manager. Screenshots end up being the naked window with a huge transparent frame. This is the case whether include decorations is ticked or unticked. This is doubtlessly very broken behavior. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 241877] Paste at cursor (instead of paste under mouse)
https://bugs.kde.org/show_bug.cgi?id=241877 Roc Vallès changed: What|Removed |Added CC||valles...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
