From: Mark Lillibridge <mdl@alum.mit.edu>
To: mdl@alum.mit.edu
Cc: eliz@gnu.org, larsi@gnus.org, 13329@debbugs.gnu.org
Subject: bug#13329: 24.2 post patch for #9521; Rmail forward does not correctly handle MIME messages containing "From " lines
Date: Mon, 10 Oct 2022 11:25:55 -0700 [thread overview]
Message-ID: <87sfjvk024.fsf@alum.mit.edu> (raw)
In-Reply-To: <87v8ork0ab.fsf@alum.mit.edu> (message from Mark Lillibridge on Mon, 10 Oct 2022 11:21:00 -0700)
If you don't want to start with an existing mbox, send a message to
yourself containing a line like "From nothing" in the body. You will
see that a > incorrectly shows up in the Rmail display due to bug
#13328. If you forward it, the > remains, which is this bug.
If you look closely, you can actually see the bug in the your
previous test -- a '>' got added in front of the From in the message you
test forwarded ('>From thing lala yes').
- Mark
next prev parent reply other threads:[~2022-10-10 18:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-01 22:24 bug#13329: 24.2 post patch for #9521; Rmail forward does not correctly handle MIME messages containing "From " lines Mark Lillibridge
2022-05-10 12:30 ` Lars Ingebrigtsen
2022-06-09 17:18 ` Lars Ingebrigtsen
2022-06-10 6:19 ` Eli Zaretskii
2022-06-10 9:24 ` Lars Ingebrigtsen
2022-06-10 11:00 ` Eli Zaretskii
2022-06-10 11:02 ` Lars Ingebrigtsen
2022-06-10 11:28 ` Eli Zaretskii
[not found] ` <83czd3l3nq.fsf@gnu.org>
2022-10-10 18:21 ` Mark Lillibridge
2022-10-10 18:25 ` Mark Lillibridge [this message]
2022-10-10 19:03 ` Eli Zaretskii
2022-10-10 19:47 ` Eli Zaretskii
2022-10-10 20:37 ` Mark Lillibridge
2022-10-11 5:24 ` Eli Zaretskii
2022-10-10 20:34 ` Mark Lillibridge
2022-10-10 21:04 ` Mark Lillibridge
2022-10-11 11:14 ` Eli Zaretskii
2023-09-03 8:33 ` Stefan Kangas
2024-01-10 11:03 ` Stefan Kangas
2022-10-11 5:20 ` Eli Zaretskii
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=87sfjvk024.fsf@alum.mit.edu \
--to=mdl@alum.mit.edu \
--cc=13329@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.