Gnus development mailing list
 help / color / mirror / Atom feed
From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: display only BBDB people in a group
Date: 29 Nov 2004 14:07:23 -0500	[thread overview]
Message-ID: <4nu0r8xyms.fsf@lifelogs.com> (raw)
In-Reply-To: <86oehg4qqx.fsf@mat.ucm.es> (Uwe Brauer's message of "Mon, 29 Nov 2004 16:30:30 +0100")

On Mon, 29 Nov 2004, oub@mat.ucm.es wrote:

> Usually I use in my nnimap-split-rules, spam-use-BBDB exclusive to
> split my imap INBOX into BBDB and non BBDB people. Although this is
> very fast on a LAN connection, on a 56K modem this can be slow.
> 
> Is there any possibility to customise the display such that only BBDB
> people or only non BBDB people  are shown. Mozilla  has such a feature
> and it looks very convenient for this circumstances.

While this is possible in the specific way you say, I wonder if a more
flexible "limit to articles that pass function X" operation might be
useful.  I didn't see such a thing in gnus-sum.el.

Ted



      reply	other threads:[~2004-11-29 19:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-29 15:30 Uwe Brauer
2004-11-29 19:07 ` Ted Zlatanov [this message]

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=4nu0r8xyms.fsf@lifelogs.com \
    --to=tzz@lifelogs.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).