From: Mike McEwan <mike@lotusland.demon.co.uk>
Subject: Re: No limit to cached '/ *'
Date: 03 May 1998 03:16:34 +0100 [thread overview]
Message-ID: <m33eescd4t.fsf@lotusland.demon.co.uk> (raw)
In-Reply-To: Harry Putnam's message of "02 May 1998 17:10:49 -0700"
Harry Putnam <reader@newsguy.com> writes:
> Wasn't there a time back down the road a bit when the command to limit
> the view to cached articles worked?
I believe you had to do a `/m RET' first. `C-h k / *' says:
/ * runs `gnus-summary-limit-include-cached'
`gnus-summary-limit-include-cached' is an alias for
`gnus-summary-insert-cached-articles', an interactive compiled Lisp
function
-- loaded from "gnus-cache.elc"
(gnus-summary-limit-include-cached)
Insert all the articles cached for this group into the current buffer.
This would appear to be exactly what it does.
--
Mike.
next prev parent reply other threads:[~1998-05-03 2:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-03 0:10 Harry Putnam
1998-05-03 2:16 ` Mike McEwan [this message]
1998-05-03 3:11 ` Harry Putnam
1998-05-03 12:58 ` Lars Magne Ingebrigtsen
1998-05-03 14:29 ` Harry Putnam
1998-05-03 16:11 ` Lars Magne Ingebrigtsen
1998-05-03 18:41 ` Harry Putnam
1998-05-04 6:56 ` Kai Grossjohann
1998-05-04 3:44 ` Paul Franklin
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=m33eescd4t.fsf@lotusland.demon.co.uk \
--to=mike@lotusland.demon.co.uk \
/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).