From: Richard Stallman <rms@gnu.org>
To: mdl@alum.mit.edu
Cc: eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: Change in rmail-insert-mime-forwarded-message
Date: Sun, 13 Jan 2013 17:43:15 -0500 [thread overview]
Message-ID: <E1TuWGp-0002yg-2G@fencepost.gnu.org> (raw)
In-Reply-To: <87d2xb64zc.fsf@foil.strangled.net> (message from Mark Lillibridge on Fri, 11 Jan 2013 08:48:07 -0800)
The obvious first step would seem to be to modify rmail-forward
(below) to have an optional argument that overrides the setting of
rmail-enable-mime-composing.
Yes, that would do it.
Unfortunately, the prefix argument is already being used to toggle
between regular forward and resend message. We could make C-u f resend
and C-u C-u f forward the non-default way, but that feels kludgy to me.
It's not ideal, but it is better than nothing.
We
could add F for the alternative forward method or move resend to its own
key, R, and make C-u f the alternative forward (not muscle memory
backwards compatible).
These are ok too,
We should probably rename (with
obsolete alias) rmail-enable-mime-composing to something like
rmail-default-forwarding-method if we do this.
With any of these changes in interface, we don't need a variable like
rmail-enable-mime-composing or rmail-default-forwarding-method, under
any name. The interface will be enough.
--
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 Ekiga or an ordinary phone call
next prev parent reply other threads:[~2013-01-13 22:43 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 [this message]
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
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=E1TuWGp-0002yg-2G@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mdl@alum.mit.edu \
/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).