unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark Lillibridge <mark.lillibridge@hp.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 9840@debbugs.gnu.org
Subject: bug#9840: 23.3; rmail-edit-current-message destroys MIME messages [SEVERE]
Date: Tue, 15 Nov 2011 10:05:52 -0800	[thread overview]
Message-ID: <qmhy5vhw9a7.fsf@hp.com> (raw)
In-Reply-To: <E1RQI3j-0002Ip-VE@fencepost.gnu.org> (message from Eli Zaretskii on Tue, 15 Nov 2011 07:24:15 -0500)


Eli Zaretskii wrote:
>  > From: Glenn Morris <rgm@gnu.org>
>  > Date: Tue, 15 Nov 2011 03:56:13 -0500
>  > Cc: 9840@debbugs.gnu.org, mark.lillibridge@hp.com
>  > 
>  > 
>  > http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9840
>  > 
>  > seems like a pretty serious problem with Emacs 23.3+'s rmail mime
>  > handling. Any ideas on how to fix this?
>  
>  Do the equivalent of `v' (rmail-mime) to get the rmail-view-buffer to
>  its original non-MIME state, let the user edit it, then replace the
>  message text in the rmail-buffer (mbox format) with the results of
>  editing, and redisplay the message?

    I think that's what 'e' should do.  Note that 'v' currently fails to
show the raw message -- I haven't had a chance to submit a complaint
about that behavior yet.  Should think about fixing bug 9841 while
you're at it.  I'm thinking at the moment we should just refuse to
accept edits that include (new) From lines, allowing the user to decide
how they want to quote them manually.  (Put point on start of From line
and signal an error?)

    In the future, (this probably qualifies as a wish list item), it
would be nice if there was a way to edit individual MIME parts.  For
example, hitting 'E' adds [edit] buttons to each MIME part.  Selecting
such a button brings up the new edit buffer with the contents of that
decoded MIME part.  After the user edited the part, it would be
re-encoded and replace the original version in the original message.
This extension would make it easy to edit printable and base64 parts.
Trying to synchronize the two buffers might be a pain though so this
extension probably needs more thought before trying implement anything.

- Mark





      parent reply	other threads:[~2011-11-15 18:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-22 18:41 bug#9840: 23.3; rmail-edit-current-message destroys MIME messages [SEVERE] Mark Lillibridge
2011-11-15  8:56 ` Glenn Morris
2011-11-15 12:24   ` Eli Zaretskii
2011-11-15 17:52     ` Glenn Morris
2011-11-16  2:10       ` Glenn Morris
2011-11-15 18:05     ` Mark Lillibridge [this message]

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=qmhy5vhw9a7.fsf@hp.com \
    --to=mark.lillibridge@hp.com \
    --cc=9840@debbugs.gnu.org \
    --cc=eliz@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).