still puzzled by what should be a common idiom

still puzzled by what should be a common idiom

[Randal L. Schwartz]

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

What I've been doing so far is

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

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

-- 
Name: Randal L. Schwartz / Stonehenge Consulting Services (503)777-0095
Keywords: Perl training, UNIX[tm] consulting, video production, skiing, flying
Email: <merlyn@stonehenge.com> Snail: (Call) PGP-Key: (finger merlyn@teleport.com)
Web: <A HREF="http://www.stonehenge.com/merlyn/">My Home Page!</A>
Quote: "I'm telling you, if I could have five lines in my .sig, I would!" -- me

Re: still puzzled by what should be a common idiom

[Aaron M. Ucko]

merlyn@stonehenge.com (Randal L. Schwartz) writes:

> & Body <ret> foo <ret> #
> (wait for searches to set mark)
> then "search" in the summary for #, which musses up if the subject has # too
> 
> What's the right ding-y way to do this?

I'd expect `/ m #' [(gnus-summary-limit-to-marks "#")] to work, but it
doesn't appear to.  Lars, would it be difficult to fix this?  Anyway,
for now I guess you could set some weird mark on all the articles with
the help of M-& and then limit to that mark.

-- 
Aaron M. Ucko, KB1CJC <amu@mit.edu> (finger amu@monk.mit.edu)

Re: still puzzled by what should be a common idiom

[Neil Crellin]

merlyn@stonehenge.com (Randal L. Schwartz) writes:
> I go into a fat folder and I want to narrow to just those
> items that have a body that matches "foo".
> 
> What I've been doing so far is
> 
> & Body <ret> foo <ret> #
> (wait for searches to set mark)
> then "search" in the summary for #, which musses up if the subject has # too
> 
> What's the right ding-y way to do this?

Sounds like you want to look into the nnir stuff.

-- 
Neil Crellin <neilc@wallaby.cc>

Re: still puzzled by what should be a common idiom

[Bill White]

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

Re: still puzzled by what should be a common idiom

[Aaron M. Ucko]

Bill White <billw@wolfram.com> writes:

> '/ 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.

Oops, that works too.  I still think `/ m #' ought to work for
consistency, though.

-- 
Aaron M. Ucko, KB1CJC <amu@mit.edu> (finger amu@monk.mit.edu)

Re: still puzzled by what should be a common idiom

[Harry Putnam]

Neil Crellin <neilc@wallaby.cc> writes:

> merlyn@stonehenge.com (Randal L. Schwartz) writes:
> > I go into a fat folder and I want to narrow to just those
> > items that have a body that matches "foo".
> > 
> > What I've been doing so far is
> > 
> > & Body <ret> foo <ret> #
> > (wait for searches to set mark)
> > then "search" in the summary for #, which musses up if the subject has # too
> > 
> > What's the right ding-y way to do this?
> 
> Sounds like you want to look into the nnir stuff.


You need to say `/ n ' after the seaches are over.
`gnus-summary-limit-to-articles'  With process (#) set gnus limits to
those articles.

Re: still puzzled by what should be a common idiom

[François Pinard]

amu@MIT.EDU (Aaron M. Ucko) writes:

> Bill White <billw@wolfram.com> writes:

> > '/ 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.

> Oops, that works too.  I still think `/ m #' ought to work for
> consistency, though.

The `mark' concept is a bit overloaded in Gnus.  `/ m' is probably meant for
`read marks' only.  I'm not sure.  Does it work for `Saved' or `Answered'
marks?  I would guess not.

-- 
François Pinard   http://www.iro.umontreal.ca/~pinard

Re: still puzzled by what should be a common idiom

[Aaron M. Ucko]

François Pinard <pinard@iro.umontreal.ca> writes:

> The `mark' concept is a bit overloaded in Gnus.  `/ m' is probably meant for
> `read marks' only.  I'm not sure.  Does it work for `Saved' or `Answered'
> marks?  I would guess not.

Good point; `/ m A RET' yields nothing in a *Summary* buffer with
several answered messages.  That just means extending its
functionality could be even more useful, thought...especially combined
with negation.

-- 
Aaron M. Ucko, KB1CJC <amu@mit.edu> (finger amu@monk.mit.edu)

Re: still puzzled by what should be a common idiom

[Kai.Grossjohann]

Randal L. Schwartz <merlyn@stonehenge.com> writes:

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

I still think that nnir.el is the way to go.  But people have reported
difficulties with it :-(  So I'd appreciate it if you tried setting up
a Glimpse index or (better still) a freeWAIS-sf index and then used
nnir.el to search it.

kai
-- 
Life is hard and then you die.

Re: still puzzled by what should be a common idiom

[Randal L. Schwartz]

>>>>> "Neil" == Neil Crellin <neilc@wallaby.cc> writes:

Neil> Sounds like you want to look into the nnir stuff.

I just installed this.  Cool!  I was already glimpsing my mail
each night... just needed a way to hook it in.

Thanks for the pointer.

-- 
Name: Randal L. Schwartz / Stonehenge Consulting Services (503)777-0095
Keywords: Perl training, UNIX[tm] consulting, video production, skiing, flying
Email: <merlyn@stonehenge.com> Snail: (Call) PGP-Key: (finger merlyn@teleport.com)
Web: <A HREF="http://www.stonehenge.com/merlyn/">My Home Page!</A>
Quote: "I'm telling you, if I could have five lines in my .sig, I would!" -- me

Re: still puzzled by what should be a common idiom

[Lars Magne Ingebrigtsen]

amu@MIT.EDU (Aaron M. Ucko) writes:

> I'd expect `/ m #' [(gnus-summary-limit-to-marks "#")] to work, but it
> doesn't appear to.

`/ n' limits to the process-marked articles.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: still puzzled by what should be a common idiom

[Jaap-Henk Hoepman]

[-- Attachment #1: Type: message/rfc822, Size: 1102 bytes --]


I once wanted to do a similar thing and was surprised to find a lot of limiting 
commands (in the menu) for matching subjects, authors, etc, but not one
for any string in the body of a message. I think it would be consistent if gnus
also had gnus-summary-limit-to-body function. 

Jaap-Henk

-- 
Jaap-Henk Hoepman             | Come sail your ships around me
Dept. of Computer Science     | And burn these bridges down
University of Twente          |       Nick Cave - "Ship Song"
Email: hoepman@cs.utwente.nl === WWW: www.cs.utwente.nl/~hoepman
Phone: +31 53 4893795 === Secr: +31 53 4893770 === Fax: +31 53 4894590
PGP ID: 0xF52E26DD  Fingerprint: 1AED DDEB C7F1 DBB3  0556 4732 4217 ABEF