From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: Restoring threads that have been read/replied to
Date: Thu, 24 Jun 2021 14:25:00 -0700 [thread overview]
Message-ID: <878s2zhs5v.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87r1gr9f07.fsf@gmail.com>
Narendra Joshi <narendraj9@gmail.com> writes:
> Alex Bennée <alex.bennee@linaro.org> writes:
>
>> Narendra Joshi <narendraj9@gmail.com> writes:
>>
>>> Alex Bennée <alex.bennee@linaro.org> writes:
>>>
>>>> Hi,
>>>>
>>>> Due to issues with gmail's IMAP handling I've switched to interacting
>>>> with my development mailing lists via gmane's archival service. I've
>>>> having some problems understanding how the thread expiration policy works.
>>>>
>>>> I've been using T k (gnus-summary-kill-thread) to kill threads I'm not
>>>> interested in. However there are a bunch of threads that I reply to or
>>>> want to keep track of. However I'm finding after I've read them they
>>>> disappear. If a reply to one of the threads appears I can't read it in
>>>> context to the rest of the thread. So a quick question:
>>>>
>>>> - can I re-fetch a whole thread based on the references in the post
>>>> that is visible in my summary?
>>>>
>>>> So far I can hi ^ (gnus-summary-refer-parent-article) and find the
>>>> parent article again but what I really want is to fetch the whole thread
>>>> with all it's context.
>>>>
>>>> Ideally this would be automatic for any thread that I've either posted
>>>> and has replies or one that I've replied to.
>>>
>>> I face the same problem a lot of times. It's very annoying. The only
>>> solutions that I could find so far are: `gnus-summary-refer-thread'
>>> (bound to `A T` in the summary buffer) and
>>> `gnus-summary-insert-old-articles' (bound to `/ o`) which I use if the
>>> former doesn't work.
>>>
>>> If you find something better, please share it in this thread and
>>> hopefully I will be able to find it later. :)
>>
>> From elsewhere in the group I currently have the following mapped to C-c
>> t in my summary-mode keymap:
>>
>> (defun my-gnus-fetch-whole-thread ()
>> "like `A R' `T o' `A T' in the summary buffer."
>> (interactive)
>> (gnus-summary-refer-references)
>> (gnus-summary-top-thread)
>> (gnus-summary-refer-thread))
>>
>>>
>>> Best,
>
> Interesting that it works for you. When I try the command in this
> thread, I get this error:
>
> Couldn’t fetch article <871r8rb2pn.fsf@gmail.com>
There's a good chance that that message is in a separate group. Maybe
you could set `gnus-refer-thread-use-search' to t and try again? That
will create a search group holding all the messages in the thread, even
if they're in separate groups now (assuming that search has been set up correctly).
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2021-06-24 21:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 12:41 Alex Bennée
2021-06-16 7:52 ` Pankaj Jangid
2021-06-24 17:19 ` Narendra Joshi
2021-06-24 20:12 ` Alex Bennée
2021-06-24 20:36 ` Narendra Joshi
2021-06-24 21:25 ` Eric Abrahamsen [this message]
2021-06-27 12:02 ` Narendra Joshi
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=878s2zhs5v.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).