🚀 go-pugleaf

Jerry writes:
 > In VM5.32, a successful vm-isearch-forward, e.g.,
 > 
 >     M-s string ESC
 > 
 > will mark a message as `read' even if it had previously been `unread'
 > or `new' and vm-preview-lines is non-nil.  Probably desireable in most
 > cases, yet ....

Maybe the attribute should be "exposed" instead of "read".
That's generally what VM means by "read".  It can't really know
wheyther you've read the message of course.

In article <9209290017.AA08041@wendy-fate.UU.NET> kyle@uunet.uu.net
(Kyle Jones) writes:

 > Maybe the attribute should be "exposed" instead of "read".
 > That's generally what VM means by "read".  It can't really know
 > wheyther you've read the message of course.

That's one of my pet peeves with vm and gnus as compared to rn.  They
mark a message read when it is first exposed.  But this is simply
wrong, as I have not yet read it (for example, I might get
interrupted).  I prefer the approach of rn, where an article is marked
'read' upon leaving it with a command whose meaning is "I've read this
one, go to the next one".


Oliver Schoett     Inst. f. Informatik (H2), Technische Univ. M"unchen
                   Postfach 20 24 20,     8000 M"unchen 2,     Germany
schoett@informatik.tu-muenchen.de    phone +49 89 2105-2399  fax -8207

Oliver Schoett writes:
Kyle> Maybe the attribute should be "exposed" instead of "read".
Kyle> That's generally what VM means by "read".  It can't really know
Kyle> wheyther you've read the message of course.

> That's one of my pet peeves with vm and gnus as compared to rn.  They
> mark a message read when it is first exposed.  But this is simply
> wrong, as I have not yet read it (for example, I might get
> interrupted).  I prefer the approach of rn, where an article is marked
> 'read' upon leaving it with a command whose meaning is "I've read this
> one, go to the next one".

Hear, Hear!  Thanks for not giving up at the phrase "of course" .
So there is a natural way of telling vm that a message has been read.

The peeve referred to is amplified when you consider previewing, where
you haven't even been "exposed" to the entire message (and you have very
little indication of that).

- Len Weisberg - weisberg@corp.hp.com - HP - Palo Alto Info Tech Center

Len Weisberg writes:
 > Oliver Schoett writes:
 > Kyle> Maybe the attribute should be "exposed" instead of "read".
 > Kyle> That's generally what VM means by "read".  It can't really know
 > Kyle> wheyther you've read the message of course.
 > 
 > > That's one of my pet peeves with vm and gnus as compared to rn.  They
 > > mark a message read when it is first exposed.  But this is simply
 > > wrong, as I have not yet read it (for example, I might get
 > > interrupted).  I prefer the approach of rn, where an article is marked
 > > 'read' upon leaving it with a command whose meaning is "I've read this
 > > one, go to the next one".
 > 
 > Hear, Hear!  Thanks for not giving up at the phrase "of course" .
 > So there is a natural way of telling vm that a message has been read.

Well, this is the way I originally implemented it, but I had
lotsa trouble deciding which commands should mark a message as
read and in what contexts.

Marking a message as read after it's been exposed seems natural
to me.  But perhaps VM is being too presumptious to even hope to
get this right.  I hate programs that are too smart for their own
good.  Maybe VM should lose this feature altogether.