From: Paul Moore <gustav@morpheus.demon.co.uk>
Subject: Re: Searching for articles
Date: Sun, 08 Dec 2002 21:23:59 +0000 [thread overview]
Message-ID: <adjgkxw0.fsf@morpheus.demon.co.uk> (raw)
In-Reply-To: <844r9ppkgj.fsf@lucy.cs.uni-dortmund.de>
kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
> M-s searches articles forward for a regexp. So go to the first
> article in the summary buffer, then M-s.
That works (although it's slow...) The main disadvantage (for me) is
that it doesn't limit the summary buffer to the matching
articles. Someone else mentioned nnir, which may answer that need,
though...
Thanks,
Paul.
--
This signature intentionally left blank
next parent reply other threads:[~2002-12-08 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <smx935yh.fsf@morpheus.demon.co.uk>
[not found] ` <844r9ppkgj.fsf@lucy.cs.uni-dortmund.de>
2002-12-08 21:23 ` Paul Moore [this message]
[not found] ` <m2fzt9qcrv.fsf@localhost.localdomain>
2002-12-08 21:50 ` Paul Moore
2002-12-09 7:37 ` Kai Großjohann
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=adjgkxw0.fsf@morpheus.demon.co.uk \
--to=gustav@morpheus.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).