After reading about the idea elsewhere, I added:
(MN) Message new scan /P /G /NOFROM /NOREAD
to my prelogin menu, so that responses pop up when logging in.

This is a nice feature, but if I read any of the messages, it resets the message read pointer so that I miss other new messages that were before the responses to me.

Anyone know of a way around that, or is that just a tradeoff I have to decide which side I prefer?

I'm having difficulty imagining how one would reasonably program that algorithm, so it wouldn't surprised me if it's not really possible.

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Storm BBS (21:2/108)

Hello Adept,

After reading about the idea elsewhere, I added:
(MN) Message new scan /P /G /NOFROM /NOREAD
to my prelogin menu, so that responses pop up when logging in.

This is a nice feature, but if I read any of the messages, it resets
the message read pointer so that I miss other new messages that were before the responses to me.

Anyone know of a way around that, or is that just a tradeoff I have to decide which side I prefer?

I added /NOLR to that command as well so it doesn't set the last read pointer when reading those messages.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Re: Prelogin check-for-echomail-responses
By: Adept to All on Fri Jun 05 2020 08:59 pm

This is a nice feature, but if I read any of the messages, it resets the message read pointer so that I miss other new messages that were before the responses to me.

This was one of the things that I didnt like Mystic. AFAIAA there is no way around it.

I'm now using Synchronet where this is not a problem. I often read new messages to me and then after replying, read "new messages". (Sometimes that means I re-read the message to me, but thats OK.)

...δεσ∩

... A pnp transistor will be an npn.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Prelogin check-for-echomail-responses
By: Al to Adept on Fri Jun 05 2020 04:07 pm

I added /NOLR to that command as well so it doesn't set the last read pointer when reading those messages.

Ahh, I just replied that I didnt like Mystic because it couldnt do this - but I didnt know this was possible.

I'm guessing the message still show as "New to you" until your last read pointer catches up?

...δεσ∩

... A raisin dropped in a glass of fresh champagne will bounce up and down continuously from the bottom of the glass to the top.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Hello alterego,

I added /NOLR to that command as well so it doesn't set the last
read pointer when reading those messages.

Ahh, I just replied that I didnt like Mystic because it couldnt do
this - but I didnt know this was possible.

Yep, the /NOLR option should probably be included on the personalscan menu by default.

I'm guessing the message still show as "New to you" until your last
read pointer catches up?

The first time you read a message addressed to yourself it will be marked as 'read' regardless of whether you read it from the personalscan menu or otherwise. The only thing the /NOLR option does is stop the last read pointers from being updated when reading messages. It should be the default behaviour (I think) so the last read pointer is not set when doing a personal scan or a regular newscan will miss unread messages previous to your last newscan.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

I added /NOLR to that command as well so it doesn't set the last read pointer when reading those messages.

Thanks! I've added it, and hopefully it works the next time I check.

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Storm BBS (21:2/108)