From: Mark Lillibridge <mdl@alum.mit.edu>
To: rms@gnu.org
Cc: eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: Change in rmail-insert-mime-forwarded-message
Date: Tue, 22 Jan 2013 16:40:42 -0800 [thread overview]
Message-ID: <87622o20l1.fsf@foil.strangled.net> (raw)
In-Reply-To: <E1TvGUJ-0004K5-Du@fencepost.gnu.org> (message from Richard Stallman on Tue, 15 Jan 2013 19:04:15 -0500)
Richard Stallman <rms@gnu.org> writes:
> > I think reverting it in the release is right.
>
> 'f' in Rmail was dysfunctional before this fix;
>
> On the contrary, it was more functional. It could forward either the
> mime-decoded message or the raw message, and did both jobs correctly.
I believe it did both incorrectly. The raw message wasn't
mbox-unescaped properly and the mime-decoded message was incorrectly
placed in a RFC822 attachment (see previous email why this causes
problems). I think Eli's real point, however, is that the need to use v
then f to forward attachments is completely nonobvious to users so
effectively Rmail doesn't support forwarding attachments pre fix in
their eyes. Arguably, this could be addressed by a comment in the news
file but if we are going to change the user interface anyways, let's do
it only once.
- Mark
next prev parent reply other threads:[~2013-01-23 0:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 2:18 Change in rmail-insert-mime-forwarded-message Richard Stallman
2013-01-07 3:44 ` Eli Zaretskii
2013-01-08 2:11 ` Richard Stallman
2013-01-09 17:15 ` Eli Zaretskii
2013-01-10 6:19 ` Richard Stallman
2013-01-10 19:03 ` Eli Zaretskii
2013-01-07 4:43 ` Mark Lillibridge
2013-01-08 2:11 ` Richard Stallman
2013-01-08 3:57 ` Mark Lillibridge
2013-01-08 10:02 ` Stephen J. Turnbull
2013-01-08 16:32 ` Mark Lillibridge
2013-01-08 18:13 ` Stephen J. Turnbull
2013-01-23 0:32 ` Mark Lillibridge
2013-01-23 6:44 ` Stephen J. Turnbull
2013-01-09 16:43 ` Richard Stallman
2013-01-10 16:53 ` Mark Lillibridge
2013-01-11 4:43 ` Richard Stallman
2013-01-11 8:10 ` Eli Zaretskii
2013-01-11 16:48 ` Mark Lillibridge
2013-01-13 22:43 ` Richard Stallman
2013-01-14 22:43 ` Richard Stallman
2013-01-15 2:13 ` Glenn Morris
2013-01-15 4:01 ` Eli Zaretskii
2013-01-15 5:27 ` Richard Stallman
2013-01-15 16:07 ` Eli Zaretskii
2013-01-16 0:04 ` Richard Stallman
2013-01-23 0:40 ` Mark Lillibridge [this message]
2013-01-15 17:29 ` Glenn Morris
2013-01-16 0:04 ` Richard Stallman
2013-01-16 1:14 ` Glenn Morris
2013-01-17 6:26 ` Mark Lillibridge
2013-01-17 21:04 ` Richard Stallman
2013-04-01 19:06 ` 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=87622o20l1.fsf@foil.strangled.net \
--to=mdl@alum.mit.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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).