* Arpad Biro <[EMAIL PROTECTED]>, 16/03/2003, 03:42 > > > A large VFS timeout can cause strange behaviour in archive file > > > handling: > > > > This is what F9 - c - e (Menu -> Command -> Free VFSs now) is for. > > Correct, but try telling this to users. They will consider this a bug > when they encounter this situation. How should they know about VFS and > such?
A quick shot in the dark, without looking at the code: would it be possible to add an mtime based sanity check for "file-based" VFSs (eg. archives, patchfs, debfs, rpmfs ... as opposed to ftpfs, smbfs, fish, ...), and enforce a "Free VFS now" if the original file has been modified since it (or its contents) was cached? Thomas -- =-------------------------------------------------------------------------= - Thomas "ZlatkO" Zajic <[EMAIL PROTECTED]> Linux-2.4.19 & Mutt-1.4i - - "It is not easy to cut through a human head with a hacksaw." (M. C.) - =-------------------------------------------------------------------------= _______________________________________________ Mc-devel mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/mc-devel
