From: Eli Zaretskii <eliz@gnu.org>
To: Mike Kupfer <mkupfer@alum.berkeley.edu>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Fix MH-E mail composition with GNU Mailutils
Date: Wed, 04 Jul 2018 19:38:24 +0300 [thread overview]
Message-ID: <83h8lfnegv.fsf@gnu.org> (raw)
In-Reply-To: <24605.1530392126@alto> (message from Mike Kupfer on Sat, 30 Jun 2018 13:55:26 -0700)
> From: Mike Kupfer <mkupfer@alum.berkeley.edu>
> cc: emacs-devel@gnu.org
> Date: Sat, 30 Jun 2018 13:55:26 -0700
>
> > Please at least explain the reason(s) for the problem. How else can
> > we reason about the necessity and risk(s) of getting this into
> > emacs-26.
>
> The problem comes about because of the way MH-E deals with some versions
> of nmh, which use a non-simple-text templating mechanism for mail
> composition, and which do not provide a convenient interface for MH-E
> mail composition. MH-E creates the draft email in a temporary folder
> and then removes the temporary folder, as part of setting up the
> composition buffer. Right now MH-E knows about the metadata file that
> nmh creates during the creation of the draft email, but Mailutils-MH has
> at least one other metadata file. So when MH-E tries to delete the
> temporary folder, the deletion errors out, which aborts the rest of the
> composition steps.
>
> > And shouldn't we invite the MH-E developers to this discussion?
>
> I posted this patch on June 7 on the MH-E developers list; see
> https://sourceforge.net/p/mh-e/mailman/mh-e-devel/?viewmonth=201806 for
> what little discussion there was.
OK, I'm sold. Thanks.
prev parent reply other threads:[~2018-07-04 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 19:00 [PATCH] Fix MH-E mail composition with GNU Mailutils Mike Kupfer
2018-06-30 19:21 ` Eli Zaretskii
2018-06-30 20:55 ` Mike Kupfer
2018-07-04 16:38 ` Eli Zaretskii [this message]
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=83h8lfnegv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mkupfer@alum.berkeley.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 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.