[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Restoring threads that have been read/replied to

From: Alex Bennée
Subject: Re: Restoring threads that have been read/replied to
Date: Thu, 24 Jun 2021 21:12:36 +0100
User-agent: mu4e 1.5.13; emacs 28.0.50

Narendra Joshi <> writes:

> Alex Bennée <> 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."

> Best,

Alex Bennée

reply via email to

[Prev in Thread] Current Thread [Next in Thread]