From: Colin Marquardt <c.marquardt@alcatel.de>
Subject: Re: Select first *unseen* unread message in summary buffer?
Date: Wed, 05 Dec 2001 10:11:20 +0100 [thread overview]
Message-ID: <k8zwv02vxon.fsf@alcatel.de> (raw)
In-Reply-To: <87y9kidxba.fsf@squeaker.lickey.com> ("Matt Armstrong"'s message of "Tue, 04 Dec 2001 22:56:41 -0700")
"Matt Armstrong" <matt+dated+1007963807.5ef3c2@lickey.com> writes:
> Daniel Pittman <daniel@rimspace.net> writes:
>
>> Hey y'all. I am curious to know if there is as (easy) way to get Gnus to
>> put point on the first /unseen/ and unread article in a summary buffer.
>>
>> Basically, what I want is that when I enter the group, Gnus places point
>> after the article that I have not read but have seen, by default.
>>
>> This way I can have articles sitting there for attention but not focus
>> them if I, for example, 'n n' in the previous group.
>
> I'm a little confused. What do you mean by "unseen"? Gnus makes a
> distinction between read and unread, with every article state other
> than unread implying that the article has been read.
It also knows about unseen: if you enter a Group which has new articles,
and then leave the Group without reading the new articles, it knows them
as seen (but unread). If you re-enter the Group again, and it has gotten
new articles in the meantime, these articles are unseen and are marked
with an "N" in the summary. This is a recent (maybe 4-6 weeks?) addition
to Oort.
Funny enough, I have at least seen that feature in the past, but not
currently. Not sure if I did something to change this, and I cannot
try a newer version since the nightly snapshots are not up-to-date
and I cannot access CVS from here.
Colin
--
"; -- is the ever important semi-colon without which Perl freaks out."
[from www.newbie.org]
next prev parent reply other threads:[~2001-12-05 9:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 5:39 Daniel Pittman
2001-12-05 5:56 ` Matt Armstrong
2001-12-05 9:11 ` Colin Marquardt [this message]
2001-12-05 9:20 ` Daniel Pittman
2001-12-05 10:37 ` Martin Monsorno
2001-12-05 11:33 ` Daniel Pittman
2001-12-05 16:51 ` Matt Armstrong
2001-12-05 8:57 ` Kai Großjohann
2001-12-05 9:22 ` Daniel Pittman
2001-12-07 14:29 ` Simon Josefsson
2001-12-08 8:56 ` Daniel Pittman
2001-12-29 1:32 ` Lars Magne Ingebrigtsen
2001-12-29 1:57 ` Lars Magne Ingebrigtsen
2002-01-14 6:17 ` Daniel Pittman
2002-01-19 22:34 ` Lars Magne Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=k8zwv02vxon.fsf@alcatel.de \
--to=c.marquardt@alcatel.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).