From: Yuri D'Elia <wavexx@users.sf.net>
To: ding@gnus.org
Subject: Reading old news
Date: Sat, 12 Feb 2011 11:35:03 +0100 [thread overview]
Message-ID: <87y65lpmlk.fsf@savara.sat.thregr.org> (raw)
Hi everyone. I'm using Gnus to read my mail from several IMAP accounts
and I whenever I need to look back into my mail archives I feel like I'm
not using Gnus optimally.
Let's say I'm looking for some old email a colleague sent me last
week. My first approach would be:
- nnir with the colleague's name, or possibly subject
- then limit to the last week with '/ t'
- look for the relevant email
- re-construct the thread with 'A T' (which doesn't seem to work too well
to me, the thread reconstruction is always partial and I need to
repeat "A T" on the parent group - yes, gather-limit is already nil).
This looks too convoluted.
Can I get the last week worth of articles from a group directly? nnir on
large groups is slow if all I need is a search in the last ~500 articles.
Right now to do that I simply enter an existing group, enter a large
(but random) number of articles to read, then limit.
Another usage pattern that I would like to optimize: let's say I'm
looking for an old conversation I had last week, I want to see all
threads that have a particular author or subject. I can search with
nnir, or open the last week-or-so of messages, but then I want to
reconstruct *all* threads I've found automatically, so that I'm getting
the big picture. Since reconstructing all threads is bothersome, I
simply read a group with a very large number of articles to read, then
(ab)use limit. I feel like I would use an "enter group with an artibrary
article limit command" feature.
Any suggestion or alternative usage pattern greatly appreciated.
Bests
next reply other threads:[~2011-02-12 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 10:35 Yuri D'Elia [this message]
2011-02-12 11:50 ` Steinar Bang
2011-02-12 19:05 ` Yuri D'Elia
2011-02-13 19:29 ` Lars Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
1996-07-14 0:44 Karl Asha
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=87y65lpmlk.fsf@savara.sat.thregr.org \
--to=wavexx@users.sf.net \
--cc=ding@gnus.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).