Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: info-gnus-english@gnu.org
Subject: Re: Multiple Message Forwarding/Attaching
Date: Fri, 20 Nov 2009 09:27:41 +0100	[thread overview]
Message-ID: <87y6m1vbwi.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <871vjt8xgj.fsf@petole.demisel.net>

Nicolas KOWALSKI <niko@petole.demisel.net> writes:

Hi Nicolas,

>>> This works when the mails to be attached are in the same group.  How
>>> do you attach mails that are stored in different groups ?
>>
>> Very good question, and I don't know how to do that in a good way.  I
>> see two workarounds:
>>
>>   a) Open a sticky article buffer for each message you want to forward,
>>      and then use `mml-attach-buffer' (C-c RET b).  But I don't know if
>>      that works if the messages contain attachments and stuff...
>
> Thanks for the idea, but how to open a "sticky" article buffer?

In a summary buffer, there is:

,----
| A S runs the command gnus-sticky-article, which is an interactive compiled Lisp
| function in `gnus-art.el'.
| 
| It is bound to A S, <menu-bar> <Article> <Make article buffer sticky>.
| 
| (gnus-sticky-article ARG)
| 
| Make the current article sticky.
| If a prefix ARG is given, ask for a name for this sticky article buffer.
`----

Also, have a look at the manual:

,----[ (info "(gnus)Sticky Articles") ]
|    This implies that it's not possible to have more than one article
| buffer in a group at a time.  But sometimes you might want to display
| all the latest emails from your mother, your father, your aunt, your
| uncle and your 17 cousins to coordinate the next christmas party.
| 
|    That's where sticky articles come in handy.  A sticky article buffer
| basically is a normal article buffer, but it won't be reused when you
| select another article.
`----

Bye,
Tassilo

  reply	other threads:[~2009-11-20  8:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-19  9:15 Volkan YAZICI
2009-11-19  9:27 ` harven
2009-11-19 11:51   ` Volkan YAZICI
2009-11-19 11:40 ` Vagn Johansen
2009-11-19 11:45 ` Tassilo Horn
2009-11-19 12:04   ` Nicolas KOWALSKI
2009-11-19 19:45     ` Tassilo Horn
2009-11-20  7:30       ` Nicolas KOWALSKI
2009-11-20  8:27         ` Tassilo Horn [this message]
2009-11-20  9:02           ` Nicolas KOWALSKI
2009-11-20 10:33             ` Tassilo Horn
2009-11-20 12:35             ` Richard Riley
2009-11-20 14:24               ` Nicolas KOWALSKI
     [not found]       ` <mailman.11125.1258702242.2239.info-gnus-english@gnu.org>
2009-11-20 11:02         ` Jens Thiele
2009-11-20 11:50           ` Nicolas KOWALSKI
2009-11-20 22:52       ` Tim Landscheidt
     [not found] ` <mailman.11039.1258631203.2239.info-gnus-english@gnu.org>
2009-11-19 11:54   ` Volkan YAZICI

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=87y6m1vbwi.fsf@thinkpad.tsdh.de \
    --to=tassilo@member.fsf.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).