From: Tassilo Horn <tassilo@member.fsf.org>
To: jidanni@jidanni.org
Cc: ding@gnus.org
Subject: Re: say best way to attach several files
Date: Thu, 20 Jan 2011 10:13:05 +0100 [thread overview]
Message-ID: <87mxmwgcpq.fsf@member.fsf.org> (raw)
In-Reply-To: <87oc7d2lkw.fsf@jidanni.org> (jidanni@jidanni.org's message of "Wed, 19 Jan 2011 19:13:03 +0800")
jidanni@jidanni.org writes:
> OK, but here and in Info say the best way to attach several files too,
> not only just one.
I use `gnus-dired-mode'. Then you can mark all files to include in
dired and then do `gnus-dired-attach' which will attach all of them to
an existing mail buffer.
,----[ C-h f gnus-dired-attach RET ]
| gnus-dired-attach is an interactive compiled Lisp function in `gnus-dired.el'.
|
| (gnus-dired-attach FILES-TO-ATTACH)
|
| Attach dired's marked files to a gnus message composition.
| If called non-interactively, FILES-TO-ATTACH should be a list of
| filenames.
`----
Bye,
Tassilo
--
Sent from my Emacs
next prev parent reply other threads:[~2011-01-20 9:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 11:13 jidanni
2011-01-20 9:13 ` Tassilo Horn [this message]
2011-01-21 2:25 ` jidanni
2011-01-22 3:01 ` Lars Ingebrigtsen
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=87mxmwgcpq.fsf@member.fsf.org \
--to=tassilo@member.fsf.org \
--cc=ding@gnus.org \
--cc=jidanni@jidanni.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).