Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Re: No limit to cached '/ *'
Date: 03 May 1998 11:41:14 -0700	[thread overview]
Message-ID: <m3wwc3fb91.fsf@org.pri> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "03 May 1998 18:11:06 +0200"

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Harry Putnam <reader@newsguy.com> writes:
> 
> > 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.
> 
> It does?
> 
> `/ v'
>      Limit the summary buffer to articles that have a score at or above
>      some score (`gnus-summary-limit-to-score').
> 
> vs.
> 
> `/ *'
>      Display all cached articles (`gnus-summary-limit-include-cached').
> 
> I thought the difference here would be self-evident.

OK, I guess I see your point. It doesn't say 'limit' but 'display"
So the only question then is why is it on a page that is explicitly
about 'Limiting?"

>From info page:
  >  Limiting
  >  
  >	  It can be convenient to limit the summary buffer to just show some
  >  subset of the articles currently in the group.  The effect most limit
  >  commands have is to remove a few (or many) articles from the summary
  >  buffer.
  >  
The name of the node is "Limiting"  <===Maybe where I got the  idea
that the commands on that page are about limiting the view.

Near as I can tell the command '/ *' does not limit in any way.

Possibly the page could be broken up into commands that actually limit
and commands that add to the display.

I may be the only one that has ever been confused by the way it is
presented.  My settings are faily common I think, eg  Caching turned on so
that ticks and dormant are cached.  This also means that cached articles
that are ticked are displayed already when entering a group because of
their 'Unread' status. So the only effect of pressing '/ *' is to
move the cursor to a cached article.

Some of my confusion has stemmed from the fact that I rarely use
dormant so didn't see anything being added by pressing '/ *'.  Now I see
that any "hidden" cached articles are indeed displayed with '/ *'.
But still not 'limited' to.

> 
> > Pressing just '/ D' does display dormant articles
> > Pressing just '/  *' does *not* display cached articles
> 
> It does for me.  When doesn't it?

When cached article are not 'hidden'.

Should have been:

 Pressing '/ m ?'<RET> does display only dormant articles
 Pressing '/ m * <RET>  does *not* display only cached articles

It displays a blank buffer.  Once you get the blank buffer you can press 
'/ *' and have a view limited to cached only.

> 
> *It's* *not* *supposed* *to*.  *It* *doesn't* *say* *that* *it's*
> *supposed* *to*.

OK point taken.  Maybe adding my suggestion for anyone who wants to
"limit" to cached only would help.  Using the '/ m' commmand with the
'*' mark does work differently than with any of the other marks.

After all, this section is about 'limiting the view to a 'subset'.

-- 

Harry Putnam  reader@newsguy.com








  reply	other threads:[~1998-05-03 18:41 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
1998-05-03 16:11         ` Lars Magne Ingebrigtsen
1998-05-03 18:41           ` Harry Putnam [this message]
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=m3wwc3fb91.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).