Version: 4.2.3 (using KDE 4.7.2) OS: Linux I thought that the read-only mode could be more useful when editing files in a different editor if the files would be automatically reloaded without prompting the user -- maybe optionally. Reproducible: Always Steps to Reproduce: - turn on read only mode - edit current file externally - return to kdevelop Actual Results: prompts for reload Expected Results: flash bang notification telling me file got reloaded. Maybe some thunder sound.
Made it a Junior Job.
Pretty sure this is an issue of katepart, and not kdevplatform.
Sven might have an idea here, as he did the auto-reload-on-git-changes thingie.
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
If you want to reduce message spam even further (for me it's very reasonable since the git-reload patch), I have had another idea, which would be automatically reloading files on change, but saving a copy of the old file somewhere (e.g. /tmp), and displaying a passive popup in the document that it was reloaded but a copy of the old buffer was saved somewhere. That is potentially problematic for large files, though.
The idea was to a edit with vim/emacs and use kdevelop for auxiliary tasks like linting, building, etc. Things kdevelop offers. Anyway, this was just an idea while exploring kdevelop and and I don't use it right now. So, given scarcity of resources, don't worry about this too much.
That's a strange usecase. I don't think there's sufficient interest in this workflow to justify implementing this feature. It's just not within the (large, but still limited) scope of what KDevelop is intended to be used for. But especially, it would be unreasonably hard to implement this in a way such that it doesn't interfere with other workflows. And doing it only when read-only mode is enabled is -- in my eyes -- a totally arbitrary choice without much logical motivation. If you really want to do this, you should rather hack it together from outside using our dbus interfaces; e.g. when your external editor changes a file, it could call a script which forces KDevelop to reload that file (there's no force reload method, but you could save the old buffer to /tmp/test.txt and then issue a reload call; would probably work well enough). I'd close this bug as invalid, ok? Greetings, Sven
Sure Greetings