From: Frank Schmitt <usereplyto2004@Frank-Schmitt.net>
Subject: Re: Sending attachments
Date: Mon, 05 Jul 2004 13:53:15 +0200 [thread overview]
Message-ID: <m33c46oel0.fsf@fed1.frank-schmitt.net> (raw)
In-Reply-To: <vw8k6xiivz8.fsf@berry.phys.ntnu.no>
Albert Reiner <areiner@tph.tuwien.ac.at> writes:
> how can I send attachments with Gnus? In the info index I only find
> entries related to handling messages with attachments that I receive.
Just to make sure that you're sufficiently confused: C-c C-a attaches a
file, too.
--
Did you ever realize how much text fits in eighty columns? If you now consider
that a signature usually consists of up to four lines, this gives you enough
space to spread a tremendous amount of information with your messages. So seize
this opportunity and don't waste your signature with bullshit nobody will read.
next parent reply other threads:[~2004-07-05 11:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <vw8k6xiivz8.fsf@berry.phys.ntnu.no>
2004-07-05 11:53 ` Frank Schmitt [this message]
[not found] ` <87eknqiv9q.fsf@koldfront.dk>
2004-07-05 12:53 ` Albert Reiner
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=m33c46oel0.fsf@fed1.frank-schmitt.net \
--to=usereplyto2004@frank-schmitt.net \
--cc=replies@Frank-Schmitt.net \
/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).