From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Like (display . all) but hide expirable messages
Date: Thu, 23 Aug 2001 20:00:25 +0200 [thread overview]
Message-ID: <m3u1yy7j2e.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87k7zwlhqy.fsf@uwo.ca>
Dan Christensen <jdc+news@uwo.ca> writes:
> 1. The docs mention both expire and expirable, but only expire works
> for me. Both should probably be permitted.
No, only the mark name is permitted. (`expire' is the name, and what
it does is mark things as expirable. :-) I've now fixed the
documentation.
> 2. The docs should say this feature is implemented by limiting the
> summary buffer, and that this means that `/ w' can be used to
> reveal the hidden articles.
I've now done so.
> 3. Would it be reasonable to have a command and keystroke that applies
> the group's (display . foo) setting to the summary buffer as it
> now stands? For example, if while reading a group some of
> the articles become marked expirable, I sometimes want to
> hide them to get rid of clutter.
Sure. I've now added this. `/ p'.
> 4. Searching the index for the word display doesn't turn up the
> Group Parameters node.
Fixed.
> 5. While in the group parameters editing screen (`G p'),
> `C-c C-i' doesn't take you to the Group Parameters node.
Ditto.
> 6. The info page includes three empty predicates:
>
> `read', `dormant', `', `', `', `expire', `reply', `killed',
Even more ditto.
> 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.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2001-08-23 18:00 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 [this message]
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=m3u1yy7j2e.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).