From: Harry Putnam <reader@newsguy.com>
Subject: Re: No limit to cached '/ *'
Date: 03 May 1998 07:29:45 -0700 [thread overview]
Message-ID: <m31zubig12.fsf@org.pri> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "03 May 1998 14:58:32 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
> > 2)Where it says:
> >
> > `/ *'
> > Display all cached articles (`gnus-summary-limit-include-cached').
> >
> > Change to:
> >
> > `/ *'
> > Display all cached articles (press '/ m <RET> / *')
> > (`gnus-summary-limit-include-cached').
> >
> > (since this is differnt than other uses of '/ m')
>
> Huh? `/ m' works on readedness marks, which is orthogonal to whether
> articles are in the cache.
If you mean the '/ m'<RET> part doesn't need to be done first to get
'/ *' to display cached articles, then I haven't found that to be true.
Haven't been able to display cached without using '/ m' first.
My only point is that on the list where the instruction about using '/ *'
appears it looks as if all you need to do is press '/ *' to limit view
to cached only. Similar to '/ D' to view dormant articles
Pressing just '/ D' does display dormant articles
Pressing just '/ *' does *not* display cached articles
What it seem to do is move the cursor to a cached article but not limit
the display to cached only.
In all other uses of '/ m' the sequence is Press '/' press 'm
Get a prompt that looks like 'Marks:' insert desired mark press <RET>
and the view gets limited to that mark.
With cache mark (*) the sequence is different.
Press '/' press 'm' Get prompt 'Marks:' press <RET> (if you insert the
'*' mark before pressing <RET> as in the other cases, you will be shown
a blank screen.)
So you must press <RET> with out inserting a mark
Now press '/ *' and view will be limited to cached
I didn't see any other way to limit the view to cached articles
So still seems to need to be clarified on the info page as in my
suggestion.
--
Harry Putnam reader@newsguy.com
next prev parent reply other threads:[~1998-05-03 14:29 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
1998-05-03 3:11 ` Harry Putnam
1998-05-03 12:58 ` Lars Magne Ingebrigtsen
1998-05-03 14:29 ` Harry Putnam [this message]
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=m31zubig12.fsf@org.pri \
--to=reader@newsguy.com \
/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).