On Tue, Apr 02, 2002 at 05:02:02PM -0500, Kyle Rawlins wrote: > On Tue, Apr 02, 2002 at 01:04:24PM -0600, David DeSimone wrote: > > Sadiq Al-Lawatia <[EMAIL PROTECTED]> wrote: > > > > > > "~/Mail/tmp/mutt-csce-4803-30 [#1] modified. Update encoding? > > > ([yes]/no): " > > > > So, the mystery here is, why does Mutt think that you're changing the > > file behind his back? Does your editor run in parallel with Mutt, like > > does it launch a separate X-window for you to edit in, while in the > > xterm where you ran Mutt, it thinks you are finished editing? That's > > the only thing I can think of. > > I notice that the tmp directory is somewhere under the home directory so could > possibly be nfs mounted - if there is a time skew between the server and the > computer running mutt this could potentially cause problems too. I am having a > hard time expressing exactly how this would work but I'm pretty sure I've seen > something like this happen to me before.
The client's clock is running a few minutes behind the server. You write the file at local noon, which the server sets to be 12:03. Mutt checks the file, sees that its mtime is in the future (12:03 being later than 12:00), and warns you. Happens regularly to me. Adam
