Mikko Hänninen writes:
> Telsa Gwynne <[EMAIL PROTECTED]> wrote on Thu, 17 Aug 2000:
> > So I get a ton of similar-style file names. In my case, they're backups
> > produced by my editor. One for each message I wrote. Most of them are
> > not empty, but are just copies of the emails I was replying to.
>
> Well, if the editor makes backups of the temporary files in /tmp, Mutt
> has no way of knowing that or to clean up afterwards. So the solution
> to this kind of problem is to turn backup creation off for the editor
> when used as Mutt's editor. Ie. an editor configuration issue, not
> really a Mutt issue (although you may need to change $editor).
>
> But I'm not sure if the files in /tmp experienced by the original poster
> are backups or not, they didn't look like the usual backups. Only he
> can tell, I suppose. On the other hand, I can't really see in which
> situation such empty files would be left behind, apart from this editor
> backups issue.
I'm afraid it is not an editor issue. I'm seeing this here as well.
They are not backups. I have not configured vi to make backups.
My *local* explanation attempt is that Solaris' unlink(2) is broken, and
has been for a while. I've seen temp files created by the man command
lying around forever, but not consistently. A www database app we've
written suffers from the same problem.
