unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 9766@debbugs.gnu.org
Subject: bug#9766: 24.0.50; rmail-forward makes attachment that doesn't read right
Date: Mon, 17 Oct 2011 09:14:44 -0400	[thread overview]
Message-ID: <E1RFn1g-00030A-AA@fencepost.gnu.org> (raw)
In-Reply-To: <E1RFfOX-0002RG-Ii@fencepost.gnu.org> (message from Eli Zaretskii on Mon, 17 Oct 2011 01:05:49 -0400)

    Actually that copying is done by
    rmail-insert-mime-resent-message
    (rmail-insert-mime-resent-message-function is set to it when
    rmailmm.el is loaded), and that function was changed by RMS
    as this.

My change was to forward the message as displayed, rather than the raw
text of the message.  I think my change eliminated the old bug.

Anyway, there is still a bug.  Some different bug.  Can someone tell
me what is wrong with the output that is generated now?  If I know
what output would be correct, I can fix this bug.

-- 
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org  www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
  Use free telephony http://directory.fsf.org/category/tel/





  reply	other threads:[~2011-10-17 13:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-16 11:19 bug#9766: 24.0.50; rmail-forward makes attachment that doesn't read right Richard Stallman
2011-10-16 12:54 ` Eli Zaretskii
2011-10-16 21:40   ` Richard Stallman
2011-10-17  5:05     ` Eli Zaretskii
2011-10-17 13:14       ` Richard Stallman [this message]
2011-10-17 14:07         ` Eli Zaretskii
2011-10-17 21:42           ` Richard Stallman
2011-10-18  1:00             ` Stefan Monnier
2011-10-18  3:54               ` Eli Zaretskii
2011-10-18 13:01                 ` Stefan Monnier
2011-10-18 13:26                   ` Eli Zaretskii
2011-10-18  3:47             ` Eli Zaretskii
2011-10-18 10:28               ` Lars Magne Ingebrigtsen
2011-10-18 10:56               ` Richard Stallman
2011-10-18  3:53             ` Eli Zaretskii
2011-10-16 18:43 ` Lars Magne Ingebrigtsen
2022-04-24 13:53 ` Lars Ingebrigtsen
2022-05-22 20:00   ` Lars Ingebrigtsen
  -- strict thread matches above, loose matches on Subject: below --
2011-09-16  7:51 bug#9521: 24.0.50; rmail-forward Kenichi Handa
2012-12-28 19:24 ` bug#9521: This bug is still present in version 24.2; it prevents forwarding correctly essentially any MINE message Mark Lillibridge
2012-12-28 20:46   ` bug#9521: PATCH for bug #9521, *not* bug #9766 Mark Lillibridge
2012-12-28 20:55   ` bug#9521: [RESEND] " Mark Lillibridge
2012-12-28 21:22     ` bug#9766: workaround for 9766 Mark Lillibridge
2012-12-29  8:53     ` bug#9521: [RESEND] PATCH for bug #9521, *not* bug #9766 Eli Zaretskii
2013-01-01 22:10 ` bug#9521: this bug (#10080) also causes an extra blank line to be appended to forwarded messages Mark Lillibridge

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=E1RFn1g-00030A-AA@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=9766@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).