Re: git-send-email: Send with mutt(1)
- From
- Alejandro Colomar <alx@kernel.org>
- Date
- Nov 9, 2023, 23:00 UTC
- Message-ID
- <ZU1kgO1SppJdNjvY@debian>
- In-Reply-To
- <20231109180308.GA2711684@coredump.intra.peff.net>
Hi Jeff,
On Thu, Nov 09, 2023 at 01:03:08PM -0500, Jeff King wrote:
Show 24 quoted lines
> 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 -"
Hmm great then! Definitely a winner. :)
Show 5 quoted lines
> > 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).
Since git-send-email allows editing, I usually edit with that. Having -E would be redundant (and in fact it felt like that to me with your suggested mutt-as-mta.sh) for my use case.
Cheers, Alex
> > -Peff
-- <https://www.alejandro-colomar.es/>