Re: Newscan Issue
  By: Aaron Thomas to All on Wed Mar 24 2021 01:04 pm

 AT> I've experienced (twice) a newscan issue with Mystic (at least with MY
 AT> Mystic.) 

 AT> I was reading messages in a public message base. Let's say I was at
 AT> message number 50 of 100.

 AT> I replied to message number 50, and I saved the message. Then I (J)umped
 AT> to message # 101 to make a quick edit to the message I just posted (the
 AT> reply.) After editing, I (Q)uit to get out of message reading.

 AT> I came back later to continue reading new messages, but this time Mystic
 AT> has my last read pointer set at message #101 (as if I already read
 AT> 50-101.) 

 AT> It seems like I tricked the system when I (J)umped to message # 101.

 AT> This isn't a big deal obviously - but has anyone else experienced this?

That's the way last read pointers work. When you jump from message 50 to 101 your last read pointer is set to 101. I get the same result here on SBBS.

 Ttyl :-),
         Al

... Cursor: An expert in four-letter words
--- SBBSecho 3.14-Linux