🚀 go-pugleaf

In article <348@bridge2.3Com.Com> ngg@bridge2.3Com.com (Norman Goodger) writes:
>In article <866@wpi.wpi.edu> jdutka@wpi.wpi.edu (John Dutka) writes:
>>It MAY be your opinion, but you know littleof the situation.  The guy saved
>>the document pretty often.  What killed the document was a crash.  Word
>>crashed, and in the process, trashed the file.  If it just saved the old doc
>>to a temp file, and THEN wrote the new file, things would have worked out
>>perfectly...

Of course if he'd been using WordPerfect, that program that all of you seem
to hate, he would have had the option of doing timed backups to a completely
different file, so even if the program does crash, as all do eventually, you
lose only a few minutes of work.  The timed backup to a separate file strikes
me as the safest method since I've lost a number of files to WriteNow when I
save and it runs out of space or crashes during the write, at which point
it has deleted the original file but not saved the new copy because of the
error.

I'll admit WordPerfect has its faults, but sticking with the Mac interface
isn't really the main one.  Word is equally, if not more so, off base when
it comes to standardization, and Word is the absolute worst program to 
consult on since you have no way of figuring out why the program is doing
something odd.  With WordPerfect, the codes make it extremely clear (with
the exception of some order problems (ie which codes come first), which
no one has quite pinned down on the PC version - I've never run into it on
the Mac version) what is happening at all times.

Adam