From: Tim Landscheidt <tim@tim-landscheidt.de>
To: info-gnus-english@gnu.org
Subject: Re: Incremental limiting in summary buffer
Date: Fri, 16 Jul 2010 17:20:16 +0000 [thread overview]
Message-ID: <m3hbjzwdgv.fsf@passepartout.tim-landscheidt.de> (raw)
In-Reply-To: <AANLkTiksd7UH4v4VpOpFgh38c9xXMPphMHsefuc6Dg3G@mail.gmail.com>
Pascal Desroche <pascal.desroche@gmail.com> wrote:
> One of the few interesting features of "classical end-user" MUA is to
> quickly find article with incremental search.
> AFAIK, today, Gnus offers "Limiting commands" in Summary buffer but
> theses commands are neither incremental nor "undo-able": If I limit
> articles that match an author (with "L a") and then realize that I was
> looking for another author, I must exit the group, enter inside it
> again, then do another "L a".
> Am I missing a more efficient method to do this?
> I don't know much elisp so maybe the idea is stupid, but would it be
> possible to use "Indirect buffers" to achieve what I want?
L a is /lowering/ (and kind of permanent); you're looking
for / a which is /limiting/. You can unlimit with / w.
Tim
prev parent reply other threads:[~2010-07-16 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 12:35 Pascal Desroche
2010-07-16 17:20 ` Tim Landscheidt [this message]
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=m3hbjzwdgv.fsf@passepartout.tim-landscheidt.de \
--to=tim@tim-landscheidt.de \
--cc=info-gnus-english@gnu.org \
/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).