[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kdevplatform] [Bug 287355] JJ: Read-only mode should not prompt but auto reload when externally edi
From:       Sven Brauch <svenbrauch () googlemail ! com>
Date:       2014-02-01 10:13:19
Message-ID: bug-287355-17878-Kh94d2qYqr () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=287355

--- Comment #4 from Sven Brauch <svenbrauch@googlemail.com> ---
Could someone enlighten me what the usecase for this is? In which case do you
have files in read-only mode and then edit them in another editor? I don't
understand the "read-only mode"  thing.

In general I'm strongly against introducing cases of reloading files in cases
where potential data loss can occur. What is an "external editor"? Is "cat" an
editor? How would you even know how the file was edited?

The "reload?" dialog has saved me from data loss more than once, especially
when redirecting output of some tool to the wrong file.

Greetings,
Sven

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]