-=> Quoting Dan Ceppa to Nancy Backus on 04-24-05  08:33 <=-

 DC> On 23 Apr 05  19:44:29, Nancy Backus got back to Dan Ceppa 
 -> Re: Toggle?
 
 NB> In 2.20 (and I'd guess also in 2.30), it's under Message Read
 NB> Preference, Inform When All Messages Read.  When set to Yes, the
 NB> default to enter is "no".  

 DC> That was easy enough!  For some reason, I thought it did something 
 DC> different...  

There's a few of them, that don't do exactly what I would have thought
it meant, but one gets used to that... 

 NB>> Just to check it out, I set it to No...  I notice that it still jumps
 NB>> to the next un-read echo, if there is more than one echo fully read,
 NB>> but not all of them...  
 DC> I think that may be a function of the "Read New Messages First".  

Could be.  :)   Not something that I would worry about... :)

 NB>> But it doesn't nag, if I choose any echo that
 NB>> has been fully read.  I normally have it set to Yes, and then override
 NB>> if I need to check something again in a fully read echo...  :)
 DC> For me, I tend to scan an Echo base and delete what I don't feel 
 DC> like reading or replying.  I then go back and read more in depth.  

I guess we all have different habits in our reading/posting... :) 
That's another good reason for having a reader that is so configurable,
being able to do things the way one wants to...    I'll read a
message base, and if I don't have time to reply at the moment, or want
to read the message in more depth later, I just toggle the read/unread
flag with "*" and come back to it later...  :)  When I come back, it
jumps right to that message.  If there's more than one in an echo
(especially a large one), I'll look for subsequent ones in the listing,
using the "T" command...  :)   Works for me... :)

ttyl              neb

... Dos Virus Scan -=Windows Found=- Delete (Y/n)

___ Blue Wave/QWK v2.20

--- ViaMAIL!/WC v1.60d