Gnus development mailing list
 help / color / mirror / Atom feed
From: Matt Armstrong <matt@lickey.com>
Cc: ding@gnus.org
Subject: Re: Automatically list groups with dormants, too
Date: Tue, 05 Feb 2002 15:23:45 -0700	[thread overview]
Message-ID: <877kpr36vi.fsf@squeaker.lickey.com> (raw)
In-Reply-To: <vafzo2of326.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 05 Feb 2002 14:53:05 +0100")

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> The key word is "automatically".  I want Gnus to hit "A p ?" for me,
> so to speak.  But the "A p" command is only good for interactive
> use.  So I wrote the following function:
>
>
> (defun kai-gnus-group-list-plus-dormant ()
>   "List groups with dormant articles in them."
>   (interactive)
>   (save-excursion
>     (let ((gnus-group-listed-groups (gnus-group-listed-groups))
> 	  (gnus-group-list-mode gnus-group-list-mode))
>       (gnus-group-list-dormant gnus-group-default-list-level))))
>
>
> Evaling (kai-gnus-group-list-plus-dormant) appears to do the right
> thing.  But I couldn't find out how to have Gnus do it automatically,
> whenever I hit `g' or `l'.

Only a stone's throw away from the pet feature I've wanted for a while
(but been too lazy to code).

I'd like to be able to set a group parameter called something like
hide-until to something like 20.  Then, that group doesn't show up in
the group buffer until it has 20 new messages in it.

I'd use this for high volume mailing lists like ding.

(right now I use group levels to hide such groups, but I still get
curious and read them too frequently.  ;-))


-- 
matt



  parent reply	other threads:[~2002-02-05 22:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-05 13:53 Kai Großjohann
2002-02-05 16:21 ` Matthieu Moy
2002-02-05 16:55 ` Ami Fischman
2002-02-05 20:40   ` Kai Großjohann
2002-02-05 21:07 ` Christoph Conrad
2002-02-06  8:02   ` Kai Großjohann
2002-02-05 22:23 ` Matt Armstrong [this message]
2002-02-06  8:32   ` Kai Großjohann
2002-02-07 16:38     ` Matt Armstrong

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=877kpr36vi.fsf@squeaker.lickey.com \
    --to=matt@lickey.com \
    --cc=ding@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).