unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mark.lillibridge@hp.com, emacs-devel@gnu.org
Subject: Re: Change in rmail-insert-mime-forwarded-message
Date: Thu, 10 Jan 2013 01:19:31 -0500	[thread overview]
Message-ID: <E1TtBUB-0008B7-B0@fencepost.gnu.org> (raw)
In-Reply-To: <83obgygtwc.fsf@gnu.org> (message from Eli Zaretskii on Wed, 09 Jan 2013 19:15:15 +0200)

    You can only send what is visible if the attachment was human-readable
    text.  You cannot do that with binary attachments.

Yes you can.  Type v, and the attachment will be visible just as it
was sent.  My change (reverting Mark's change) will add functionality
and lose none.

So I think I should do this -- the arguments against it seem
not to be based on a mistaken idea of the effects.

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




  reply	other threads:[~2013-01-10  6:19 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 [this message]
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
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=E1TtBUB-0008B7-B0@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mark.lillibridge@hp.com \
    /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).