Version: 3.5.5-r1 (using KDE KDE 3.5.5) OS: Linux It would be awesome if Kate could load files from an SVN instead of disk, and commit them back to the repository on save, rather than saving to disk. This would eliminate some of the hastle involved in using local svn repositories for configuration files and small projects. As it is now, people have to make changes, save changes, test changes, make changes, save changes, (etc), commit. Test some more, If there is a problem, roll back. Saving to svn would reduce it to: make changes, save/commit. Test, if there is a problem, roll back. It would be very convenient :) Thanks
This should have been wishlist, sorry.
Sounds like a prime candidate for a KIOslave. In fact, I'm not sure what other way would make sense to implement this...
On Thursday 31 May 2007, Nathan Spaeth wrote: Kate can save/load to any protocol known to KDE. So if you know the correct URL, and your system defines a svn:/ protocol with load/save functionality, you can. In my opinion, such a protocol would be a wiser addition than hacking functionality into KatePart.
Well, there's already an svn ioslave in kdesdk, but thats really more a ioslave-wrapped svn-commandline tool. So I guess this should be re-assigned to kdesdk to ask for an ioslave that is capable of doing simple load/save.
As pointed out by Andreas Pakulat, an SVN kioslave exists, which may or may not address your request (try protocols svn:// svn+ssh://, etc.). Then there's also bug #116770 for more elaborate subversion support. Could you clarify a bit, what functionality you are looking for above that provided by the svn kioslave? Depending on that, this request should probably either be closed, merged with #116770 or re-assigned to kio to make sure the right people take a look at it. Thanks!
One note: If you re-assign, make sure to re-assign to kdesdk and the svn ioslave lives there not in kdelibs where the kio component exists.
Other option: use the external tools plugin with kate to commit, with kdialog for retrieving a commit message.
Well, since there was no clarification by the reporter, I'll mark this as a duplicate of bug #116770. *** This bug has been marked as a duplicate of 116770 ***