Gnus development mailing list
 help / color / mirror / Atom feed
From: Dan Christensen <jdc+news@uwo.ca>
Subject: Re: Like (display . all) but hide expirable messages
Date: Wed, 13 Feb 2002 17:30:14 -0500	[thread overview]
Message-ID: <871yfp2ex5.fsf@uwo.ca> (raw)
In-Reply-To: <2n7kph1gds.fsf@zsh.cs.rochester.edu> (ShengHuo ZHU's message of "Wed, 13 Feb 2002 11:43:59 -0500")

ShengHuo ZHU <zsh@cs.rochester.edu> writes:

> Dan Christensen <jdc+news@uwo.ca> writes:
>
>> ShengHuo ZHU <zsh@cs.rochester.edu> writes:
>>
>>> Dan Christensen <jdc+news@uwo.ca> writes:
>>>
>>>> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>>>>
>>>>> Dan Christensen <jdc+news@uwo.ca> writes:
>>>>>
>>>>>> 7. I can't get (display . [and (not expire) (not read)]) or
>>>>>>    (display . [and (not expire) unread]) to work for me.  With
>>>>>>    the former I get prompted to input a Lisp Expression when I
>>>>>>    enter a group.
>>>>>
>>>>> So much ditto that I don't know how to express it.
>>>>>
>>>>>>    With the latter I get the following error when 
>>>>>>    entering a group:
>>>>>>
>>>>>> Debugger entered--Lisp error: (void-function unread)
>>>>>>   unread()
>>>>>
>>>>> I've now made that invalid and removed it from the documentation.
>>>>
>>>> This still doesn't work for me, with a cvs from an hour ago.  (not
>>>> read) checks that the article doesn't appear in gnus-newsgroup-reads,
>>>> but this variable seems to keep track of the articles read in the
>>>> *current* session, so I think it is always nil when the summary is
>>>> being generated.  What I want is to check that the article is in
>>>> gnus-newsgroup-unreads.  So I think read should be made invalid, and
>>>> unread should be made valid, since it is what one is actually
>>>> interested in.
>>>
>>> I added unread.
>>
>> It still doesn't work for me, with the latest cvs.
>
> What are the evaluations of gnus-summary-display-cache and
> gnus-category-predicate-cache ?

Here they are.  The first doesn't mention unread.

gnus-summary-display-cache's value is shown below.

Documentation:
not documented as a variable.

Defined in `gnus-sum'.

Value:
((seen .
       #[nil "\300\301!\207"
	     [gnus-article-marked-p seen]
	     2])
 (recent .
	 #[nil "\300\301!\207"
	       [gnus-article-marked-p recent]
	       2])
 (forward .
	  #[nil "\300\301!\207"
		[gnus-article-marked-p forward]
		2])
 (unsend .
	 #[nil "\300\301!\207"
	       [gnus-article-marked-p unsend]
	       2])
 (download .
	   #[nil "\300\301!\207"
		 [gnus-article-marked-p download]
		 2])
 (cache .
	#[nil "\300\301!\207"
	      [gnus-article-marked-p cache]
	      2])
 (save .
       #[nil "\300\301!\207"
	     [gnus-article-marked-p save]
	     2])
 (score .
	#[nil "\300\301!\207"
	      [gnus-article-marked-p score]
	      2])
 (dormant .
	  #[nil "\300\301!\207"
		[gnus-article-marked-p dormant]
		2])
 (bookmark .
	   #[nil "\300\301!\207"
		 [gnus-article-marked-p bookmark]
		 2])
 (killed .
	 #[nil "\300\301!\207"
	       [gnus-article-marked-p killed]
	       2])
 (expire .
	 #[nil "\300\301!\207"
	       [gnus-article-marked-p expire]
	       2])
 (reply .
	#[nil "\300\301!\207"
	      [gnus-article-marked-p reply]
	      2])
 (tick .
       #[nil "\300\301!\207"
	     [gnus-article-marked-p tick]
	     2])
 (unseen .
	 #[nil "\300\301!\207"
	       [gnus-article-marked-p unseen]
	       2])
 (read .
       #[nil "\300\301!\207"
	     [gnus-article-marked-p read]
	     2]))

gnus-category-predicate-cache's value is shown below.

Documentation:
not documented as a variable.

Defined in `gnus-agent'.

Value:
(((not expire)
  .
  #[nil "\300\301!?\207"
	[gnus-article-marked-p expire]
	2])
 ((and
   (not expire)
   (not read))
  .
  #[nil "\300\301!?\205\v
	[gnus-article-marked-p expire read]
	2])
 ((not read)
  .
  #[nil "\300\301!?\207"
	[gnus-article-marked-p read]
	2])
 (unread . unread)
 ((and
   (not expire)
   unread)
  .
  #[nil "\300\301!?\205	
	[gnus-article-marked-p expire unread]
	2])
 ((and
   (not expire)
   (unread))
  .
  #[nil "\300\301!?\205	
	[gnus-article-marked-p expire nil]
	2]))

-- 
Dan Christensen
jdc+news@uwo.ca



  reply	other threads:[~2002-02-13 22:30 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
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 [this message]
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=871yfp2ex5.fsf@uwo.ca \
    --to=jdc+news@uwo.ca \
    /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).