From: Tassilo Horn <tsdh@gnu.org>
To: info-gnus-english@gnu.org
Subject: Re: Show group for article found via search?
Date: Tue, 25 Sep 2012 10:50:19 +0200 [thread overview]
Message-ID: <87wqzicwqc.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <87obkumvom.fsf@slate.zedat.fu-berlin.de>
"Loris Bennett" <loris.bennett@fu-berlin.de> writes:
> [mail]
> [general]
> nnimap+mail.my.provider.com:INBOX
> nnimap+mail.my.provider.com:sent
> [work]
> nnimap+mail.my.provider.com:this
> nnimap+mail.my.provider.com:that
> nnimap+mail.my.provider.com:theother
> [private]
> nnimap+mail.my.provider.com:friends
> nnimap+mail.my.provider.com:family
> [news]
> ...
>
> If I use G G on a topic to search for a message and get several
> results, is there a way to find out which folder each message found is
> in?
I think, there's no way to see that information from the nnir search
results summary. But you can "warp" to any article found in its
originating group:
,----[ (info "(gnus)Basic Usage") ]
| The `nnir' group made in this way is an `ephemeral' group, and some
| changes are not permanent: aside from reading, moving, and deleting,
| you can't act on the original article. But there is an alternative: you
| can _warp_ to the original group for the article on the current line
| with `A W', aka `gnus-warp-to-article'. Even better, the function
| `gnus-summary-refer-thread', bound by default in summary buffers to `A
| T', will first warp to the original group before it works its magic and
| includes all the articles in the thread. From here you can read, move
| and delete articles, but also copy them, alter article marks, whatever.
| Go nuts.
`----
Bye,
Tassilo
next prev parent reply other threads:[~2012-09-25 8:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 7:02 Loris Bennett
2012-09-25 8:50 ` Tassilo Horn [this message]
2012-09-25 12:26 ` Andrew Cohen
2012-09-25 15:20 ` Tassilo Horn
[not found] ` <mailman.9694.1348563048.855.info-gnus-english@gnu.org>
2012-09-25 11:22 ` Loris Bennett
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=87wqzicwqc.fsf@thinkpad.tsdh.de \
--to=tsdh@gnu.org \
--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).