unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Alfred M. Szmidt" <ams@gnu.org>
To: emacs-devel@gnu.org
Subject: rmail and mime encoded patches annoyance
Date: Fri, 19 May 2023 02:11:03 -0400	[thread overview]
Message-ID: <E1pztKR-0001Lx-2v@fencepost.gnu.org> (raw)

Hi,

Was working through a set of patches, and sorta got a bit fed up, more
often than not patches are sent as MIME attachment, and show up as:

[2:text/plain Show Save:patch-foo-bar-baz.lisp (6kB)]

in the RMAIL buffer.  But if you edit such a message
(rmail-edit-current-message); it is very cumbersome to edit it
attachments, since they will be in base64, and you need to decode
manually.  Plus, when viewing the message later .. it will no longer
be expanded.

Is there some way of "decoding the message" permantnetly into ASCII or
something, so that it now longer is MIME encoded?  So you get "What I
See Is What I Edit" behaviour..  This would then also be useful when
one replies to such messages with inline comments to a patch.

/Alfred



             reply	other threads:[~2023-05-19  6:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-19  6:11 Alfred M. Szmidt [this message]
2023-05-19  6:45 ` rmail and mime encoded patches annoyance Eli Zaretskii
2023-05-19  7:17   ` Alfred M. Szmidt
2023-05-19 10:51     ` Eli Zaretskii
2023-05-19 11:08       ` Alfred M. Szmidt
2023-05-19 11:25         ` Eli Zaretskii
2023-05-19 11:31           ` Alfred M. Szmidt
2023-05-19 11:38             ` Eli Zaretskii
2023-05-19 11:39           ` Alfred M. Szmidt
2023-05-19 16:53             ` Bob Rogers
2023-05-21  0:46               ` Francesco Potortì

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=E1pztKR-0001Lx-2v@fencepost.gnu.org \
    --to=ams@gnu.org \
    --cc=emacs-devel@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).