Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Get \201 when I edit mail
Date: 04 Feb 1999 00:11:00 +0100	[thread overview]
Message-ID: <m33e4ncccb.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Stainless Steel Rat's message of "03 Feb 1999 14:22:24 -0500"

Stainless Steel Rat <ratinox@peorth.gweep.net> writes:

> Given the recent discussion in the gnu.emacs newsgroups, I am under the
> impression that this is actually a bug in MULE. 

Well -- it has more to do with how Gnus de/encodes things "manually".

I've been thinking quite a bit about how to do article editing, and I
just can't see any way to allow that in an elegant way -- especially
with MIME gunk and MULE gunk in the way.

The two possible approaches that I see are these:

1) When editing a MIME message, not necessarily a multipart one, but
   that as well, we plop the user into something that looks more or
   less like a Message buffer with the article in.  Multipart articles
   are transformed into MML (text parts just get a "part" marker
   before them and non-text parts get a part that has the contents in
   an external file).  When finishing the editing, Gnus does what
   Message does -- transforms the MML back into MIME.

   This approach means that the user has little actual control over
   the details of the resulting article.  For instance, parts of the
   result may be base64-d, etc.

2) Do a `C-u g' before the editing, and let the user edit the
   completely raw article.

I don't really see any middle road.

Of course, if we have 1), we also must have 2).  But 1) will be a
major bitch to write, I think.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen


  parent reply	other threads:[~1999-02-03 23:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-03 14:12 Nicolas Morais
     [not found] ` <m3u2x3b8cv.fsf@peorth.gweep.net>
1999-02-03 23:11   ` Lars Magne Ingebrigtsen [this message]
     [not found]     ` <m31zk79f5g.fsf@peorth.gweep.net>
1999-02-04  1:08       ` Lars Magne Ingebrigtsen
1999-02-15  2:22         ` Hallvard B Furuseth
1999-02-15  2:26           ` Hallvard B Furuseth
1999-02-19 14:19           ` Lars Magne Ingebrigtsen
1999-02-21 17:31           ` François Pinard
1999-02-26  6:58             ` Lars Magne Ingebrigtsen
1999-02-04  4:23     ` Michael Welsh Duggan
1999-02-04  4:28       ` Michael Welsh Duggan
1999-02-04 16:57       ` 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=m33e4ncccb.fsf@quimbies.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).