Gnus development mailing list
 help / color / mirror / Atom feed
From: Bill White <billw@wolfram.com>
Cc: merlyn@stonehenge.com
Subject: Re: still puzzled by what should be a common idiom
Date: 06 Jul 1999 17:36:16 -0500	[thread overview]
Message-ID: <ruobtdps8wv.fsf@g.wolfram.com> (raw)
In-Reply-To: merlyn@stonehenge.com's message of "06 Jul 1999 11:08:44 -0700"

In article <m11zelmz0z.fsf@halfdome.holdit.com>, merlyn@stonehenge.com (Randal L. Schwartz) writes:

  randal> I go into a fat folder and I want to narrow to just those
  randal> items that have a body that matches "foo".

  randal> What I've been doing so far is

  randal> & Body <ret> foo <ret> #
  randal> (wait for searches to set mark)
  randal> then "search" in the summary for #, which musses up if the subject has # too

  randal> What's the right ding-y way to do this?

'/ n' narrows to articles marked with #. You can then use '/ w' to
widen the Summary buffer back to the way it was before the narrowing.

Thanks to Kai who posted this once upon a time.

Well, here's larsi's explanation from the manual at Gnus->The Summary
Buffer->Limiting:

`/ n'
     Limit the summary buffer to the current article
     (`gnus-summary-limit-to-articles').  Uses the process/prefix
     convention (*note Process/Prefix::.).

`/ w'
     Pop the previous limit off the stack and restore it
     (`gnus-summary-pop-limit').  If given a prefix, pop all limits off
     the stack.

bw
--
Bill White . billw@wolfram.com . http://members.wri.com/billw


  parent reply	other threads:[~1999-07-06 22:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-06 18:08 Randal L. Schwartz
1999-07-06 18:43 ` Aaron M. Ucko
1999-07-08  7:04   ` Lars Magne Ingebrigtsen
1999-07-06 19:32 ` Neil Crellin
1999-07-06 23:10   ` Harry Putnam
1999-07-07 22:32   ` Randal L. Schwartz
1999-07-06 22:36 ` Bill White [this message]
1999-07-06 23:04   ` Aaron M. Ucko
1999-07-06 23:34     ` François Pinard
1999-07-07  1:41       ` Aaron M. Ucko
1999-07-07  9:55 ` Kai.Grossjohann
1999-07-07  7:21 Jaap-Henk Hoepman

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=ruobtdps8wv.fsf@g.wolfram.com \
    --to=billw@wolfram.com \
    --cc=merlyn@stonehenge.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).