From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Editing article
Date: 30 Nov 1998 15:40:04 +0100 [thread overview]
Message-ID: <m3btlpckhn.fsf@sparky.gnus.org> (raw)
In-Reply-To: Steinar Bang's message of "30 Nov 1998 09:27:52 +0100"
Steinar Bang <sb@metis.no> writes:
> Just as a test I did "e" on an article containing an image. I was
> curious what I would see: naked MIME or MML. It looked like MML.
Well, it was probably neither -- just the raw, displayed article.
> However, I didn't see any traces of the image and the image was gone
> and the MML only half translated back when I did C-c C-c.
>
> What's the plan for article editing?
I don't know, really... One way would be to transform the article
from MIME to MML, but that would be a lot of work. But I don't really
see any other option...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-11-30 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-30 8:27 Steinar Bang
1998-11-30 14:40 ` Lars Magne Ingebrigtsen [this message]
1998-11-30 15:03 ` Hrvoje Niksic
1998-11-30 16:48 ` Lars Magne Ingebrigtsen
1998-11-30 16:33 ` Steinar Bang
1998-11-30 17:13 ` Lars Magne 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=m3btlpckhn.fsf@sparky.gnus.org \
--to=larsi@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).