Re: Can git send-email support neomutt?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2022-11-06 at 08:58:20, Wu Zhenyu wrote:
> Thanks for your quick reply.

Hi, please keep the list in CC.  It's helpful that everyone can benefit
from seeing the replies, and it's possible someone else might have a
thought on a good way forward.

> > You can also use `git format-patch --stdout | neomutt -f -` and that may
> > provide you the same functionality you were hoping for with
> > `sendemail.sendmailCmd`.
> 
> It cannot use `git send-email -1` I like.
> 
> > Mutt and Neomutt are MUAs, which stands for mail user agent.  That is,
> > they're mail clients that people use to read, compose, and send email.
> 
> People can use MUA to send email, the only problem is `-i`. I consider the following method

Sure, I agree that we can do so.  In fact, as soon as I'm done composing
this email, I'll be using mutt to send that.

> ```
> [sendemail]
> 	suppresscc = author
> 	sendmailCmd = git-neomutt
> ```
> 
> `~/.local/bin/neomutt`
> 
> ```
> #!/usr/bin/env bash
> neomutt "${@//-i/}"
> ```
> 
> And it can work:
> 
> ```
> ❯ git send-email -1
> /tmp/5441yKUviQ/0001-TEST.patch
> The following files are 8bit, but do not declare a Content-Transfer-Encoding.
>     /tmp/5441yKUviQ/0001-TEST.patch
> Which 8bit encoding should I declare [UTF-8]?
> To whom should the emails be sent (if anyone)? my-another@email
> Message-ID to be used as In-Reply-To for the first email (if any)?
> Logging in...
> Warning: Fcc to an IMAP mailbox is not supported in batch mode
> Skipping Fcc to imaps://imaphz.qiye.163.com/Sent
> OK. Log says:
> Sendmail: git-neomutt -i my-another@email
> From: Wu Zhenyu <wuzhenyu@xxxxxxxx>
> To: my-another@email
> Subject: [PATCH] TEST
> Date: Sun,  6 Nov 2022 16:39:49 +0800
> Message-Id: <20221106083949.210946-1-wuzhenyu@xxxxxxxx>
> X-Mailer: git-send-email 2.38.1
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
> 
> Result: OK
> ```

There's nothing here preventing you from invoking an arbitrary program.
That program just has to implement a sendmail-compatible interface,
which neomutt doesn't.  If you want to wrap neomutt in a
sendmail-compatible interface like you've done, then this can work just
fine.

> I want to know can we remove `-i` to allow more MUA/MTA? If user want to add something, why not let them
> 
> ```
> [sendemail]
> 	sendmailCmd = msmtp -i
> ```

This breaks a lot of the existing tooling which expects that this is a
sendmail-compatible interface.  In addition, we might add an additional
value in the future, like -B8BITMIME (which we really should be adding
if we're sending 8bit data).  The documentation specifically says it
should be sendmail-like.

> I think it should be easy to realize.

I think this is going to cause a bunch of compatibility problems.  git
send-email is specifically designed to cause email to be sent (i.e., via
SMTP).  If you want to use another tool to do the sending, that's fine,
but then you typically want to use git format-patch to provide those to
the other program.

> And I'll consider share this tip to neomutt.
> 
> Thanks!

-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux