unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#9840: 23.3; rmail-edit-current-message destroys MIME messages [SEVERE]
@ 2011-10-22 18:41 Mark Lillibridge
  2011-11-15  8:56 ` Glenn Morris
  0 siblings, 1 reply; 6+ messages in thread
From: Mark Lillibridge @ 2011-10-22 18:41 UTC (permalink / raw)
  To: 9840


    In gnuemacs 23.3.1 (or earlier?), displaying of MIME text parts got
turned on by default.  E.g., buttons like:

[1/1:text/plain Hide]

appear in the message body displayed followed by the decoded text part.

    When you invoke message editing via 'e', rmailedit.el assumes
(mistakenly) that it is dealing with a normal message body (e.g., not
decoded) and lets you edit the buttons and decoded text.  Far, far
worse, when you finish editing, rmailedit.el replaces the original valid
message with the decoded text!  This destroys all the nontext parts and
put the button text in the message itself.  Worse, if you realize
something is wrong and attempt to abort the edit via ^c^[, your message
is still destroyed since rmail-abort-edit just restores the "message
text" (e.g., the decoded view) then calls the normal edit exit code
(rmail-cease-edit).  To add to the fun, if you attempt to abort editing
by killing the rmail buffer, you will lose any other changes made to
that mbox file, including the incorporation of new mail.

Executive summary: if you press 'e' (even accidentally) in Rmail mode
while viewing a MIME message, it will be destroyed the matter what you
do.

- Mark





^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#9840: 23.3; rmail-edit-current-message destroys MIME messages [SEVERE]
  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
  0 siblings, 1 reply; 6+ messages in thread
From: Glenn Morris @ 2011-11-15  8:56 UTC (permalink / raw)
  To: Kenichi Handa; +Cc: 9840, mark.lillibridge


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?

(It happens in 23.3 as well, so is not related to bug#9520.)





^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#9840: 23.3; rmail-edit-current-message destroys MIME messages [SEVERE]
  2011-11-15  8:56 ` Glenn Morris
@ 2011-11-15 12:24   ` Eli Zaretskii
  2011-11-15 17:52     ` Glenn Morris
  2011-11-15 18:05     ` Mark Lillibridge
  0 siblings, 2 replies; 6+ messages in thread
From: Eli Zaretskii @ 2011-11-15 12:24 UTC (permalink / raw)
  To: Glenn Morris; +Cc: 9840, mark.lillibridge

> 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?





^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#9840: 23.3; rmail-edit-current-message destroys MIME messages [SEVERE]
  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
  1 sibling, 1 reply; 6+ messages in thread
From: Glenn Morris @ 2011-11-15 17:52 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: 9840, mark.lillibridge

Eli Zaretskii wrote:

> Do the equivalent of `v' (rmail-mime) to get the rmail-view-buffer to
> its original non-MIME

I think your method is right; except currently this doesn't work because
of bug#9520.

>  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?





^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#9840: 23.3; rmail-edit-current-message destroys MIME messages [SEVERE]
  2011-11-15 12:24   ` Eli Zaretskii
  2011-11-15 17:52     ` Glenn Morris
@ 2011-11-15 18:05     ` Mark Lillibridge
  1 sibling, 0 replies; 6+ messages in thread
From: Mark Lillibridge @ 2011-11-15 18:05 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: 9840


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





^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#9840: 23.3; rmail-edit-current-message destroys MIME messages [SEVERE]
  2011-11-15 17:52     ` Glenn Morris
@ 2011-11-16  2:10       ` Glenn Morris
  0 siblings, 0 replies; 6+ messages in thread
From: Glenn Morris @ 2011-11-16  2:10 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: 9840, mark.lillibridge

Glenn Morris wrote:

> Eli Zaretskii wrote:
>
>> Do the equivalent of `v' (rmail-mime) to get the rmail-view-buffer to
>> its original non-MIME
>
> I think your method is right; except currently this doesn't work because
> of bug#9520.

Actually 9520 does not seem to be relevant, because rmail-mime does not
seem to offer a way to show the raw message. Toggling rmail-mime off is
not the same as viewing a message with rmail-enable-mime nil. The mime
boundaries are always absent.

Anyway, I installed something that hopefully stops rmailedit destroying
messages. I hope Rmail users will test it.

Feel free to rip this out and replace it with something more elegant...





^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2011-11-16  2:10 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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

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).