From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: Select first *unseen* unread message in summary buffer?
Date: Sat, 08 Dec 2001 19:56:48 +1100 [thread overview]
Message-ID: <87snamccof.fsf@inanna.rimspace.net> (raw)
In-Reply-To: <ilubshbp0h3.fsf@dhcp128.extundo.com> (Simon Josefsson's message of "Fri, 07 Dec 2001 15:29:44 +0100")
On Fri, 07 Dec 2001, Simon Josefsson wrote:
> 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.
>
> Can you score up "unseen" (and possibly "recent" as well) articles and
> then use ',' (`gnus-summary-best-unread-article')?
Not without losing some of the filtering I currently use to work out
what is and isn't worth reading.
I probably can, but I would rather implement a more flexible interface
to selecting the first article, I admit. :)
Daniel
--
The string is a stark data structure and everywhere it is passed there
is much duplication of process. It is a perfect vehicle for hiding
information.
-- Alan J. Perlis, _Epigrams in Programming_ (September, 1982)
next prev parent reply other threads:[~2001-12-08 8:56 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
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 [this message]
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=87snamccof.fsf@inanna.rimspace.net \
--to=daniel@rimspace.net \
/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).