Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Like (display . all) but hide expirable messages
Date: Fri, 17 Aug 2001 18:56:13 +0200	[thread overview]
Message-ID: <m3sneqy6aa.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m3elqkapnd.fsf@multivac.cwru.edu>

prj@po.cwru.edu (Paul Jarc) writes:

> To take it even further, e.g.:
> (display . (and (not expire) (or tick (not read))))

Neat.

> But this might be more than is worthwhile.

Has that ever stopped us before?  :-)

So, the question is -- what marks should be predicatable?  (If that's
not a word, I just made it one.)

These are the ones that are stored in the .newsrc.eld file:

(defconst gnus-article-mark-lists
  '((marked . tick) (replied . reply)
    (expirable . expire) (killed . killed)
    (bookmarks . bookmark) (dormant . dormant)
    (scored . score) (saved . save)
    (cached . cache) (downloadable . download)
    (unsendable . unsend) (forwarded . forward)
    (recent . recent)))

I could make a general predicate that takes an article number and a
type, but the function would just be one big cond, or I could define

gnus-article-marked-p, gnus-article-replied-p, gnus-article-expirable-p

and so on.

If a general predicate (which might actually be easier to use, in this
case), it would be called `gnus-article-marked-p'.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen


  reply	other threads:[~2001-08-17 16:56 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-09 16:49 Kai Großjohann
2001-08-09 16:57 ` Jody Klymak
2001-08-09 20:38 ` Nuutti Kotivuori
2001-08-09 21:18 ` Leonard Stiles
2001-08-09 21:28   ` Paul Jarc
2001-08-17 16:56     ` Lars Magne Ingebrigtsen [this message]
2001-08-17 17:24       ` Kai Großjohann
2001-08-17 17:36         ` Lars Magne Ingebrigtsen
2001-08-09 22:41   ` Kai Großjohann
2001-08-17 16:48   ` Lars Magne Ingebrigtsen
2001-08-17 17:24     ` Kai Großjohann
2001-08-17 17:36       ` Lars Magne Ingebrigtsen
2001-08-17 18:40         ` Lars Magne Ingebrigtsen
2001-08-22  6:40           ` Dan Christensen
2001-08-23 18:00             ` Lars Magne Ingebrigtsen
2001-08-24  2:02               ` Dan Christensen
2001-08-24  4:43                 ` ShengHuo ZHU
2001-08-24 14:03                 ` Lars Magne Ingebrigtsen
2001-08-24 17:33                   ` Dan Christensen
2001-08-24 21:52                     ` Björn Torkelsson
2002-02-11  4:29               ` Dan Christensen
2002-02-13  3:27                 ` ShengHuo ZHU
2002-02-13 15:57                   ` Dan Christensen
2002-02-13 16:43                     ` ShengHuo ZHU
2002-02-13 22:30                       ` Dan Christensen
2002-02-13 22:48                         ` ShengHuo ZHU
2002-02-15 20:06                           ` Dan Christensen
2001-08-17 19:13     ` Leonard Stiles
2001-08-17 19:29       ` Lars Magne Ingebrigtsen
2001-08-14 21:28 ` Wes Hardaker
2001-08-15  2:07 ` Dan Christensen

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=m3sneqy6aa.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).