mikshaw


Group: Members
Posts: 4856
Joined: July 2004 |
 |
Posted: Nov. 10 2007,15:05 |
 |
Probably, but it seems a LOT of applications leave their temp files behind, expecting you to take care of them with your regularly scheduled mantenance. The problem here, as far as I see it, is more in the way emelfm creates the temp files rather than the way it removes them. As with a handful of other programs, it seems to assume a single-user system, with a single set of temp files. A more considerate application would create .emelfm-unpack-$USER, or .emelfm-unpack-$UID, instead of just .emelfm-unpack
You could add sudo rm -rf /tmp/.emelfm-unpack/* to your emelfm launcher (icon, menu item, whatever you use) so it would automatically remove previous temp files, if this happens often enough to annoy you.
Personally I dislike the way Emelfm handles archives. I find it very annoying that it would suggest repacking temp files over the original, particularly in the majority of cases where the files haven't been touched in the first place.
-------------- http://www.tldp.org/LDP/intro-linux/html/index.html
|