From: Tassilo Horn <tassilo@member.fsf.org>
To: Gnus Beta Testers <ding@gnus.org>
Subject: Re: Archiving messages and nnir
Date: Thu, 08 Mar 2012 12:44:12 +0100 [thread overview]
Message-ID: <87d38nxqpf.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <m21up39vck.fsf@xemacs.org> (Didier Verna's message of "Thu, 08 Mar 2012 12:37:47 +0100")
Didier Verna <didier@xemacs.org> writes:
Hi Didier,
> I've just ran on a small inconvenience a minute ago.
>
> - My mails are stored on a imap server.
> - I wanted to reply to an old message, so I did a 'G G' on a group, and
> found the message in question.
> - I replied to it, but the X-Draft-From header is set to 'nnir
> something' instead of the original group the message came from.
>
> As a consequence, Gnus could not archive my reply properly. I have no
> time to look into this right now, so if someone wants to beat me to
> it...
When you've found the message you've been looking for in the nnir
buffer, hit `A W' or `A T' on it and you'll switch to that message (or
complete thread) in the original imap group. Then all your posting
styles and archive settings apply as usual.
,----[ (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-03-08 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 11:37 Didier Verna
2012-03-08 11:44 ` Tassilo Horn [this message]
2012-03-08 12:35 ` Didier Verna
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=87d38nxqpf.fsf@thinkpad.tsdh.de \
--to=tassilo@member.fsf.org \
--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).