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 07:08:17 -0400 [thread overview]
Message-ID: <E1pzxy5-0005Nt-Cl@fencepost.gnu.org> (raw)
In-Reply-To: <83pm6wtx0c.fsf@gnu.org> (message from Eli Zaretskii on Fri, 19 May 2023 13:51:15 +0300)
Buffers aren't permanent. I'd need to save the buffer to a file, to
later re-open, and then send -- possibly also remove the file when
done. RMAIL already keeps tabs on what messages I've replied to or
not, or have edited. And I get all of that just in one go, when I
edit a message. I can label messages, and show only specific ones
based on labels.
Adding FCC/BCC is an extra additional step that is very easy to
forget, which also involves actually sending your email, and fetching
your email -- so a permanent network connection.
All the suggestions are additional work, work which did not exist
before MIME. It is neither incremental, nor inuitive if you are
already familiar with rmail-edit.
I too review lots of patches (about 20-30 per day), and this is only
annoying when people send them as something that is not "text", and
was hoping to minimize that work using a workflow that has worked for
decades -- so I'm not that interested in other ways of working, rather
figuring out how one could fix rmail-edit so that it continues to
work.
next prev parent reply other threads:[~2023-05-19 11:08 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
2023-05-19 10:51 ` Eli Zaretskii
2023-05-19 11:08 ` Alfred M. Szmidt [this message]
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=E1pzxy5-0005Nt-Cl@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 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).