Hi Stephen
"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
For practical purposes, XEmacs never exits, so this requirement
amounts to "XEmacs needs to know when the file is not needed any
more." And we know that's difficult.
Not deleting files in $TMPDIR when an application exits, based on some
unfounded claim that a certain application doesn't exit is silly.
By that logic, I'd claim that since I never reboot my PC (I don't even
log out), a "tmpreaper" would never get a chance to clean $TMPDIR.
Unless run via a cron job, that is, which would still derail
applications accessing files in $TMPDIR.
And no, checking atime does not help either. There simply is no
perfect way.
Only a simple list of file names would be necessary, each (file name)
element of which would be unlinked when XEmacs exits. To protect from
the biggest blunders the expanded names could be required to be
relative to $TMPDIR. If *your* XEmacs doesn't exit -- fine, you'll
have the same behaviour as you proposed with not deleting files at
all. But those who do occasionally exit XEmacs will have $TMPDIR
ridded of all residue XEmacs created.
Best regards
Marcus
--
note that "property" can also be used as syntaxtic sugar to reference
a property, breaking the clean design of verilog; [...]
(seen on
http://www.veripool.com/verilog-mode_news.html)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta