It has a global directory /var/tmp/jove where it dumps recover and temporary files, unlike vi's .swp files which are in the same directory as the file being edited.
So I'm wondering how best to handle files in /var/tmp/jove, which could be important in case the editor may have crashed and somebody wants to recover files from them.
A couple of different methods of dealing with them that I see:
1) Having remove leave /var/tmp/jove alone and having purge delete /var/tmp/jove. However, isn't purge for configuration files and not for temporary files?
2) Have a PreRmScript which tries to rmdir /var/tmp/jove. If there's something in there, then rmdir fails and PreRmScript can ask the user to D)elete it, L)eave it alone, or Q)uit and fail the remove.
3) Leave the files and /var/tmp/jove there regardless if remove or purge is used.
I like 2, but then people aren't used to having a PreRmScript take user input, are they?
3) Would be nice if OS X cleaned up old files in /var/tmp/jove after they are unread for two weeks like RedHat's tmpwatch package.
What's the best way of handling this?
Blair
-- Blair Zajac <[EMAIL PROTECTED]> Plots of your system's performance - http://www.orcaware.com/orca/
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
