On Fri 02 Jan 2004 15:44, Richard Eibrand wrote:
>> AKAIK, he was using nedit to edit the file, which proceeded to have a
> sh**fit after he tried the compilation (and is still troubling him)... and
> no he didnt have the incremental backup option enabled...
>
Still troubling him? If he continued using the machine after the incident,
AFAIK there's very little chance of any of the undeletion tools other people
have pointed to working, I'm afraid. One really needs to stop, unmount the
filesystem, and run the undeletion tool ASAP.
Re: nedit autobackup, which AFAIK defaults to on - did he really manually
disable it? Silly. Nedit defaults to keeping a backup in filename "~name.c"
(yes the tilde is at the other end of the name to emacs, e.g. say if the file
is in your home dir, you might use a silly looking "~/\~name.c" to access
it.)
If nedit had a sh**fit it might well be because the incrementally updated
backup that it keeps in ~name.c++ suddenly stopped corresponding to
name.c++ while it was running - e.g. if he ran the g++ command line in another
window.
http://www.nedit.org/help/recovery.shtml#Crash_Recovery
All in all though, it's the kind of mistake you make once and then stop
making... Having said that, I'm a heretic that thinks that in this day and
age of absurdly huge harddrives typical linux distro filesystems should think
about built-in backup/versioning.
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
