Re: Marking read articles (was Small complaint about M-g)

[Jussi Yli-Urpo <jmy@h32.erkki.ton.tut.fi>]

Chris Brierley <brierley@pobox.com> writes:
> I go to an article, before I'm done reading it something
> comes up, and without thinking I quit the buffer (or
> whatever), do the something else, and I've "missed" that
> article because it's now marked as read.

That is extactly the case I'm worried about. For me, mail
should not be marked as read before it actually *is* read.

> I just thought, wouldn't it be nice if there was an option to only
> mark the current article as read *after* you've completed reading
> it. 

> So, it's still automatically marked, but there is less of
> a chance of you "losing" an article you haven't read
> thoroughly.

This would be really nice. I also thought this solution but
I didn't at least found any existing hook to use.

> Off the top of my head I can see that it might be difficult to
> decide what constituted "read completely".  For instance, what
> would you do on the last unread article of a group?  Normally
> hitting 'q' should not mark the current article as read because
> you might not be done with it, but, for the last article in a
> group you'd need it to.  Hrm.

In case of last message in Group would it be enought to mark
it read when you reach the end of article and get the
message "No more unread acticles"?

> Does anyone have any thoughts on this, or ideas on how to
> implement it?

So, how about adding hook which is called when end of
article is reached?

Well, after thinking more about this solution I don't still
know would this be safe enough to use. I just don't trust
myself so much... :)

> Just thinking.

Me too...

-- 
Jussi.