[comp.mail.mush] Bug in Headers Command

mer6g@uvaarpa.virginia.edu (Marc Rouleau) (03/06/90)

When I process a folder that initially contains more than one screen
of headers and delete messages to the point that all the remaining
ones could fit on a single screen, the headers command no longer
displays message #1.  I can type "h 1", and that works, but "h"
displays all remaining messages except #1.

This is the case with 7.0.4, but I don't think it's a new bug.

    -- Marc Rouleau

randall@uvaarpa.virginia.edu (Randall Atkinson) (03/07/90)

Marc Rouleau's description sounds like what I see under 
Mush 6.5.something here and at edison.cho.ge.com.
So it probably isn't new.

  Ran
  randall@virginia.edu

schaefer@ogicse.ogi.edu (Barton E. Schaefer) (03/07/90)

In article <3036@uvaarpa.virginia.edu> mer6g@uvaarpa.Virginia.EDU (Marc Rouleau) writes:
} When I process a folder that initially contains more than one screen
} of headers and delete messages to the point that all the remaining
} ones could fit on a single screen, the headers command no longer
} displays message #1.  I can type "h 1", and that works, but "h"
} displays all remaining messages except #1.

OK, I just fixed it, but if you expect to keep your sanity, don't spend too
long looking at the algorithm that figures out how to make "headers" work.
(If it were just a matter of counting forward and skipping deleted messages,
it wouldn't be bad, but to handle all the options and so on it has to be
able to count forward then backward or backward then forward or ....)

} This is the case with 7.0.4, but I don't think it's a new bug.

It's a new bug that happens to have the same symptoms as an old one.
There are a lot of other cases in which messages can be omitted in older
versions of mush.
-- 
Bart Schaefer          "EARTH: Surrender IMMEDIATELY or we PICKLE DAN QUAYLE"

                                                                    "THPPFT!"
schaefer@cse.ogi.edu (used to be cse.ogc.edu)