From: William F Hammond <hammond@csc.albany.edu>
To: info-gnus-english@gnu.org
Subject: Re: png in message, reply and preview `preview-copy-region-as-mml'
Date: Fri, 25 Jan 2008 11:40:25 -0500 [thread overview]
Message-ID: <i7ejc5j1ty.fsf@hilbert.math.albany.edu> (raw)
In-Reply-To: <mailman.6529.1201274666.18990.info-gnus-english@gnu.org>
Uwe Brauer <oub@mat.ucm.es> writes:
>>>>>> "David" == David Kastrup <dak@gnu.org> writes:
> ...
> >> deletes it. I presume that has to do with the fact that gnus send
> >> messages as plain text.
>
> > Hardly. C-c C-f can forward PNGs just fine.
>
> You are right, however
> `gnus-summary-reply-with-original'
> does not and I can't see any way to include these png the same way
> forwarding does that.
From the summary buffer I use
'gnus-summary-followup-with-original' (key: F)
or
'gnus-summary-followup' (key: f)
Then mml-attach-file from the message composition buffer (key: C-c RET f)
or (Menu: Attachments->Attach File)
Its doc is this:
mml-attach-file is an interactive compiled Lisp function in `mml'.
(mml-attach-file FILE &optional TYPE DESCRIPTION DISPOSITION)
Attach a file to the outgoing MIME message.
The file is not inserted or encoded until you send the message with
`C-c C-c' or `C-c C-s'.
FILE is the name of the file to attach. TYPE is its content-type, a
string of the form "type/subtype". DESCRIPTION is a one-line
description of the attachment.
You'll be prompted for type, description, and disposition.
The doc should say that disposition is one of "attachment" or "inline"
or ... (I'm not sure if there are other choices -- tab at the prompt
to check)
-- Bill
next prev parent reply other threads:[~2008-01-25 16:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.6525.1201266737.18990.info-gnus-english@gnu.org>
2008-01-25 14:28 ` David Kastrup
2008-01-25 15:24 ` Uwe Brauer
[not found] ` <mailman.6529.1201274666.18990.info-gnus-english@gnu.org>
2008-01-25 16:40 ` William F Hammond [this message]
2008-01-25 18:03 ` Ted Zlatanov
2008-01-27 10:12 ` Uwe Brauer
2008-01-25 13:11 Uwe Brauer
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=i7ejc5j1ty.fsf@hilbert.math.albany.edu \
--to=hammond@csc.albany.edu \
--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).