From: "Alfred M. Szmidt" <ams@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: rmail and mime encoded patches annoyance
Date: Fri, 19 May 2023 03:17:27 -0400 [thread overview]
Message-ID: <E1pzuMh-0007DI-9Y@fencepost.gnu.org> (raw)
In-Reply-To: <83sfbsu8el.fsf@gnu.org> (message from Eli Zaretskii on Fri, 19 May 2023 09:45:06 +0300)
> 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.
Not that I know of, no. MIME capabilities in Rmail are minimal, and
do 90% of the job very well, but not much more.
FWIW, I almost never use rmail-edit, and don't really understand why
it's useful, let alone when a MIME patch is attached to it. If what
you need is to edit the patch before applying it,
It is more for commenting about the patch, in this case. One could
start a new reply, but those aren't presitent, and sometimes patches
take a week or two to go over.
Similar, I use this for longer responses, where I edit the message and
add my reply/comments/... and then save the RMAIL buffer. And when
you're done, you just reply with the notes you did.
Alas MIME is more and more prevailant, Rmail Edit sorta has gotten
more and more cumbersome to use. :(
then (a) that is not really recommended, since you will be applying
code attributed to someone else with your own changes; and (b) you
could always copy the patch to another buffer, edit it there, and
then apply.
Doing that multiple times a day gets old quick; was hoping to find a
better way.
next prev parent reply other threads:[~2023-05-19 7:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 6:11 rmail and mime encoded patches annoyance Alfred M. Szmidt
2023-05-19 6:45 ` Eli Zaretskii
2023-05-19 7:17 ` Alfred M. Szmidt [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1pzuMh-0007DI-9Y@fencepost.gnu.org \
--to=ams@gnu.org \
--cc=eliz@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 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.