|
From: | David Levine |
Subject: | Re: [Nmh-workers] Locking (specifically, sequences) |
Date: | Sat, 09 Mar 2013 09:32:54 -0500 |
Ken wrote: > >> So it probably makes sense to there to call seq_read() to read/lock > >> the sequence file after all the messages are searched; that will > >> reload any changes to the sequence file & write-lock it. > > > >What happens if there were changes to the sequence file, > >esp. some that invalidate the (potentially long) operation > >that had just been completed? > > I'm trying to imagine how that would work. Programs like "pick" and > "inc" just add sequences to the the sequence file. So what could > be happening that would invalidate what they do? * a "show" that removed a message from the unseen sequence * a "mark" that removed anything from any sequence that they use * a "refile" that made a heckuva mess David
[Prev in Thread] | Current Thread | [Next in Thread] |