From: Alejandro Colomar <alx@kernel.org>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: git-send-email: Send with mutt(1)
Date: Fri, 10 Nov 2023 14:30:49 +0100 [thread overview]
Message-ID: <ZU4widBlHljjg9lL@debian> (raw)
In-Reply-To: <ZU1-l4PwMU5H4_VN@debian>
[-- Attachment #1: Type: text/plain, Size: 2964 bytes --]
On Fri, Nov 10, 2023 at 01:51:34AM +0100, Alejandro Colomar wrote:
> Hi Jeff,
>
> On Thu, Nov 09, 2023 at 01:03:08PM -0500, Jeff King wrote:
> > On Thu, Nov 09, 2023 at 04:26:23PM +0100, Alejandro Colomar wrote:
> >
> > > I've tried something even simpler:
> > >
> > > ---8<---
> > > #!/bin/sh
> > >
> > > mutt -H -;
> > > --->8---
> > >
> > > I used it for sending a couple of patches to linux-man@, and it seems to
> > > work. I don't have much experience with mutt, so maybe I'm missing some
> > > corner cases. Do you expect it to not work for some case? Otherwise,
> > > we might have a winner. :)
> >
> > Wow, I don't know how I missed that when I read the manual. That was
> > exactly the feature I was thinking that mutt would need. ;)
> >
> > So yeah, that is obviously better than the "postponed" hackery I showed.
> > I notice that "-H" even causes mutt to ignore "-i" (a sendmail flag that
> > Git adds to sendemail.sendmailcmd). So you can just invoke it directly
> > from your config like:
> >
> > git config sendemail.sendmailcmd "mutt -H -"
>
> Having it directly in sendmailcmd causes some glitch: It repeats all CCs
> in TO. See a log:
>
> Send this email? ([y]es|[n]o|[e]dit|[q]uit|[a]ll): y
> OK. Log says:
> Sendmail: mutt -H - -i kevin@8t8.us mutt-dev@mutt.org alx@kernel.org e.sovetkin@gmail.com neomutt-devel@neomutt.org
> From: Alejandro Colomar <alx@kernel.org>
> To: Kevin McCarthy <kevin@8t8.us>,
> mutt-dev@mutt.org
> Cc: Alejandro Colomar <alx@kernel.org>,
> Jenya Sovetkin <e.sovetkin@gmail.com>,
> neomutt-devel@neomutt.org
> Subject: [PATCH] send.c: Allow crypto operations in batch and mailx modes.
> Date: Fri, 10 Nov 2023 01:41:24 +0100
> Message-ID: <20231110004128.5972-2-alx@kernel.org>
> X-Mailer: git-send-email 2.42.0
> MIME-Version: 1.0
> Content-Transfer-Encoding: 8bit
>
> Result: OK
>
> The sent mail ended up being
>
> From: Alejandro Colomar <alx@kernel.org>
> To: Kevin McCarthy <kevin@8t8.us>, mutt-dev@mutt.org, alx@kernel.org,
> e.sovetkin@gmail.com, neomutt-devel@neomutt.org
> Cc: Alejandro Colomar <alx@kernel.org>,
> Jenya Sovetkin <e.sovetkin@gmail.com>, neomutt-devel@neomutt.org
>
> So maybe we need the wrapper script to ignore the arguments.
Heh! The following trick works as well, without needing a script:
[sendemail]
sendmailcmd = mutt -H - && true
It probably relies too much on git-send-email(1)'s current
implementation, but it works. :)
Cheers,
Alex
>
> Cheers,
> Alex
>
> >
> > Annoyingly, "-E" doesn't work when reading over stdin (I guess mutt
> > isn't willing to re-open the tty itself). But if you're happy with not
> > editing as they go through, then "-H" is then that's enough (in my
> > workflow, I do the final proofread via mutt).
> >
> > -Peff
>
> --
> <https://www.alejandro-colomar.es/>
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-11-10 13:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 11:14 git-send-email: Send with mutt(1) Alejandro Colomar
2023-11-07 17:48 ` Jeff King
2023-11-07 18:36 ` Alejandro Colomar
2023-11-07 20:16 ` Jeff King
2023-11-08 21:02 ` Alejandro Colomar
2023-11-08 21:27 ` Jeff King
2023-11-09 15:26 ` Alejandro Colomar
2023-11-09 16:08 ` Konstantin Ryabitsev
2023-11-09 17:42 ` Alejandro Colomar
2023-11-09 17:59 ` Konstantin Ryabitsev
2023-11-10 21:06 ` Alejandro Colomar
2023-11-09 18:03 ` Jeff King
2023-11-09 23:00 ` Alejandro Colomar
2023-11-10 0:51 ` Alejandro Colomar
2023-11-10 13:30 ` Alejandro Colomar [this message]
2023-11-10 21:41 ` Jeff King
2023-11-10 23:31 ` Junio C Hamano
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=ZU4widBlHljjg9lL@debian \
--to=alx@kernel.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.
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 NNTP newsgroup(s).