Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!apple!rutgers!soleil!slopoke.semi.harris-atd.com!thrush!del
From: del@thrush.semi.harris-atd.com (Don Lewis)
Newsgroups: comp.mail.mush
Subject: Re: current message location after folder update
Message-ID: <1989Dec7.033725.23815@semi.harris-atd.com>
Date: 7 Dec 89 03:37:25 GMT
References: <1989Dec6.031050.12607@semi.harris-atd.com> <5995@ogicse.ogc.edu>
Sender: news@semi.harris-atd.com
Reply-To: del@thrush.semi.harris-atd.com (Don Lewis)
Organization: Harris Semiconductor, Melbourne, FL
Lines: 23

In article <5995@ogicse.ogc.edu> schaefer@ogicse.UUCP (Barton E. Schaefer) writes:
>In article <1989Dec6.031050.12607@semi.harris-atd.com> del@thrush.semi.harris-atd.com (Don Lewis) writes:
>} It would be real nice if when a folder is updated, the current message
>} location is preserved, rather than setting the current message back to
>} the beginning of the folder.  This is gets a little tricky if the

>
>It gets a little tricky if *any* messages preceding the current one are
>deleted, let alone if the current one is deleted.  The current message
>is stored only as an offset into an array of messages, and that array
>is completely flushed and reloaded by an update.  It might be possible
>to do some arithmetic in the process of re-writing the folder to compute
>what the "new" current message number should be ....

This is pretty much what I had in mind.  It doesn't look like it should be
all that hard to figure out what the new message number should be.  I haven't
looked at how hard it will be to get mush to use this when it reloads the
folder, though.
--
Don "Truck" Lewis                                     Harris Semiconductor
Internet (if you're lucky): del@semi.harris-atd.com   PO Box 883   MS 62A-028
Internet (if not): del%thrush@trantor.harris-atd.com  Melbourne, FL  32901
UUCP (works): rutgers!soleil!thrush!del               Phone: (407) 729-5205