Gnus development mailing list
 help / color / mirror / Atom feed
From: Mark Thomas <swoon@bellatlantic.net>
Cc: Thomas Skogestad <tskogest@jusstud.uio.no>, ding@gnus.org
Subject: Re: Annoying new features in newer Oorts
Date: Tue, 14 May 2002 10:30:52 -0400	[thread overview]
Message-ID: <wf1k7q6by60.fsf@svelte.home> (raw)
In-Reply-To: <vafwuupxwyq.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>

On Tue, 30 Apr 2002, Kai.Grossjohann@CS.Uni-Dortmund.DE wrote:

> Thomas Skogestad <tskogest@jusstud.uio.no> writes:
> 
>> 1. When entering a group buffer, and I specify that I want to read
>>    read messages also, Gnus goes to the first unread message, not
>>    to the beginning of the buffer.
> 
> There's a variable for this.  Hm.  It's not gnus-auto-select-first,
> but similar.  Can't remember right now.  But I'm sure it's in the
> GNUS-NEWS file.

Are you thinking of gnus-auto-select-subject?

  Documentation:
  *Says what subject to place under point when entering a group.
  
  This variable can either be the symbols `first' (place point on the
  first subject), `unread' (place point on the subject line of the first
  unread article), `best' (place point on the subject line of the
  higest-scored article), `unseen' (place point on the subject line of
  the first unseen article), 'unseen-or-unread' (place point on the subject
  line of the first unseen article or, if all article have been seen, on the
  subject line of the first unread article), or a function to be called to
  place point on some subject line.

-Mark



  parent reply	other threads:[~2002-05-14 14:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3229147191814452@oakhurst.yi.org>
2002-04-30  9:34 ` Sean Neakums
     [not found]   ` <3229150801659975@oakhurst.yi.org>
2002-04-30 11:14     ` Romain FRANCOISE
2002-04-30 11:53       ` Fabien Penso
2002-04-30 11:39     ` Matthieu Moy
2002-04-30 11:48       ` Sean Neakums
     [not found]       ` <3229343185064781@oakhurst.yi.org>
2002-05-02 15:49         ` Sean Neakums
2002-05-02 16:32           ` Karl Eichwalder
2002-05-02 17:59             ` Florian Weimer
2002-05-03  7:38             ` Sean Neakums
2002-05-03 15:05               ` Karl Eichwalder
2002-05-03 17:50                 ` Kai Großjohann
2002-05-03 21:23                   ` Matt Armstrong
2002-05-03 21:30                   ` Matt Armstrong
2002-05-04  1:19                     ` Karl Eichwalder
2002-05-04 13:48                     ` Sean Neakums
2002-05-04 14:01                       ` Florian Weimer
2002-05-04 14:05                         ` Sean Neakums
2002-05-05 12:02                     ` Kai Großjohann
2002-05-05 13:29                     ` Steinar Bang
2002-05-05 15:18                       ` Simon Josefsson
2002-05-05 13:19               ` Steinar Bang
2002-05-05 13:14     ` Steinar Bang
2002-04-30 11:10 ` Martin Sandiford
2002-04-30 11:11 ` Kai Großjohann
2002-05-14 10:48   ` Andreas Fuchs
2002-05-14 14:30   ` Mark Thomas [this message]
2002-05-14 14:54     ` Andreas Fuchs
2002-05-14 15:24     ` Kai Großjohann
2002-04-30 13:05 ` Kai Großjohann

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=wf1k7q6by60.fsf@svelte.home \
    --to=swoon@bellatlantic.net \
    --cc=ding@gnus.org \
    --cc=tskogest@jusstud.uio.no \
    /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).