Hello,
I know there is this very popular file version control program 'git' and can use that and have also used that.
But already working a few last years mainly with SubVersion.
The main and basically sole purpose here for me is for backup purposes of files to edit in TSE.
Each time I change something in some program which I edit in TSE
(e.g. text files like foobar.c, foobar.cpp, foobar.s,
foobar.si,
foobar.html, foobar.txt, ...) I store it automatically via a TSE menu option
in a SubVersion database for backup purposes.
I can then e.g. very quickly do a diff test with an earlier backup version, optionally rollback to an
earlier version and can add comments to remember later about what has changed.
So I tweeked the original svn.s file so that when I run the 'svn.mac' macro it will immediately
(without further key input)
*automatically* select (almost always) the current filename in the (here very long) list of programs
so one does not have to search for that filename in that long list anymore.
I can then press <F5> to see a list of revisions and select those of interest.
(I have already described the steps it more in full in an earlier email sent:
I was looking at implementing something similar for SubVersion as I created for GIT.
What I wanted to do was e.g. comparing the diff of 2 revisions from within TSE.
Then came across this TSE SVN macro.
And that possible behavior was already built in in that svn.s macro, out of the box for me.
1. Run the program
2. Point to your Subversion repository (for some reason, not further investigated how it did find that) it did find that automatically on my system, so nothing needed to be done).
3. Put the cursor on the file of interest in that list
4. Press <F5> to see all the revisions of that file of interest.
5. Put your cursor on the revision of interest
6. press <ENTER> to load/edit that revision file into TSE.
7. Repeat step 5 and 6 to load the second revision file of interest into TSE
8. Then run a program like BeyondCompare or TSE CmpBuffers to see any differences.
9. Then work from there, e.g. editing, saving and saving the result into a latest revision file into SubVersion.
So if you should be using SubVersion for your file version control this should be really VERY HANDY
and it will thus support very good in keeping and maintaining backups of any of the involved (text) files.
You might be able to change your local svn.s accordingly. E.g. using a diff between the 2 files and changing it to
your local conditions on your system.
I use thus Cygwin svn.exe to handle the SubVersion commands. It is really extremely stable.
Download the original svn.s
and see attached
my (changed from that original) svn.s
with friendly greetings
Knud van Eeden