From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Select first *unseen* unread message in summary buffer?
Date: Sat, 29 Dec 2001 02:32:47 +0100 [thread overview]
Message-ID: <m3k7v6vmio.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87snamccof.fsf@inanna.rimspace.net>
Daniel Pittman <daniel@rimspace.net> writes:
> I probably can, but I would rather implement a more flexible interface
> to selecting the first article, I admit. :)
`gnus-auto-select-first' is the variable that controls this, and it's
a bit of a mess.
----------
gnus-auto-select-first's value is
gnus-summary-first-unread-subject
Documentation:
*If nil, don't select the first unread article when entering a group.
If this variable is `best', select the highest-scored unread article
in the group. If t, select the first unread article.
This variable can also be a function to place point on a likely
subject line. Useful values include `gnus-summary-first-unread-subject',
`gnus-summary-first-unread-article' and
`gnus-summary-best-unread-article'.
If you want to prevent automatic selection of the first unread article
in some newsgroups, set the variable to nil in
`gnus-select-group-hook'.
----------
So, it really controls two things at once.
1) It says what subject line to place point on
2) It says whether that article should be selected as well
That's nasty.
I suggest splitting this up into two variables.
1) gnus-auto-select-subject, which says what subject line point
should be placed on
2) gnus-auto-select-article, which says whether the article should
be selected
Better variable names should be selected, but I think I'll just go
ahead and make this change. The variables can get their default
values from the obsolete `gnus-auto-select-first' variable, if that's
set.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2001-12-29 1:32 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
2001-12-29 1:32 ` Lars Magne Ingebrigtsen [this message]
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=m3k7v6vmio.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
/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).