Not an 'issue' or 'bug', but another technique to explore

[synthesizerpatel]

Hi, just wanted to share this with you if you weren't aware of it. If you use an Apache based SVN server, there's a configuration setting you can enable 'autoversioning' as described in http://svnbook.red-bean.com/en/1.7/svn.webdav.autoversioning.html

By default, SVN exposes itself as a WebDAV filesystem which Windows,Linux and OSX all natively support as a 'first-class' filesystem that can be mounted/read/write/unmounted transparently to applications - when you enable autoversioning, any time you save a file it will automatically check it in to SVN.

The only caveat with this method is that Windows and OSX both use tmp files as a standard precaution against nuking files - so when you save a file from an application, it'll open up a tmp file, write it all out, close it and then do an atomic rename to replace the 'real file'. That way there's no chance of losing your content. The result being that your SVN log gets 2 'actions' for every time you save a file, a create and a rename. But, if you're ok with that, and you control the SVN server you're connecting to - it's another way to accomplish the same thing.

Obviously this method vs. your application serve different purposes, and I'm not suggesting that you stop persuing the app. Just wanted to share as it's been a nifty trick I've used in non-standard situations like editing audio fiiles where I wanted to be able to have 'versions' no matter what.

That's a really clever solution! Part of the purpose of this tool for me was a way to push the file to a server and then be able to refresh my browser and immediately see the change. Is there a setting or tool for that updates the server's workspace every time the repo is committed to? I suppose an SVN hook could be used for that too, if an existing config or solution doesn't exist.