|
From: Wendy S <wen...@co...> - 2002-03-16 21:52:09
|
On Saturday 16 March 2002 h:55, Slava Pestov wrote: > Maybe the cause of the slowdown is the large number of backup files > created? They must all be renamed, to increment their backup number > by one. I see... I didn't realize it rolled them so that 1 is the most recent backup. That makes sense! I'll put it back at a reasonable number and try it again on Monday. Please do consider implementing the backup for FTP files. :) Is there a way to "force" a backup, other than using 'Save a Copy As'? Backups every 30 seconds or 1 minute are less useful than my being able to take a snapshot of working code before I make a change. I'm not using the backups as an 'undo' feature, but almost as versions, so I can go back to a working version if I mess it up. Chances are, that was more than 2.5 minutes (default 5 copies * 30 seconds) ago. Hmm... and with that said I'd like to take a snapshot of all of the open buffers so that they "match". Could be it's time to figure out how to use something that does version control... any suggestions? I'm working on my first fairly large project, so I don't know how to keep track of it. Basically I need to get it working, set a copy of the whole thing aside, then keep working, probably breaking it and fixing it again, set a copy of THAT aside, etc. So that when one of my team members asks to see it, I can point them at the most recent working version, not say, "Oh, it's broken right now, I'll let you know when it's working again!" -- Wendy in Chandler, AZ wendywds * at % cox # dot ) net |