git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Can git send-email support neomutt?

From
Wu Zhenyu <wuzhenyu@ustc.edu>
Date
Nov 6, 2022, 09:02 UTC
Message-ID
<20221106090233.ukf6rjzrygpnavzh@desktop>
In-Reply-To
<Y2anAijZxu9QEX4M@tapette.crustytoothpaste.net>
Thanks for your quick reply.
> 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
```
[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@ustc.edu>
To: my-another@email
Subject: [PATCH] TEST
Date: Sun,  6 Nov 2022 16:39:49 +0800
Message-Id: <20221106083949.210946-1-wuzhenyu@ustc.edu>
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
```
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
```
I think it should be easy to realize.
And I'll consider share this tip to neomutt.
Thanks!
On Sat, Nov 05, 2022 at 06:10:10PM +0000, brian m. carlson wrote:
Show 32 quoted lines
> On 2022-11-05 at 15:46:00, Wu Zhenyu wrote:
> > Excuse me.
> > 
> > I want to use neomutt as git send-email's cmd:
> > 
> > ```
> > [sendemail]
> > 	sendmailCmd = neomutt
> > ```
> 
> 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.
> The sendmailCmd wants an MTA, or mail transfer agent, which is
> essentially a mail server.  It's customary for most Unix systems to have
> such a piece of software which emulates the original Sendmail in its
> command-line interface, even if that's to send data off the system.
> 
> That's why you see a fixed interface here, because whether someone is
> using Sendmail, Exim, Postfix, or a smarthost-only tool like esmtp-run,
> whatever software is being used presents the same interface.
> 
> It's not likely that we'd add a lot of customizability to this option.
> However, you can use the same SMTP server that you use with Neomutt by
> setting the smtpuser, smtpencryption, smtpserver, and smtpserverport
> options.
> 
> 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`.
> -- 
> brian m. carlson (he/him or they/them)
> Toronto, Ontario, CA
-- 
Best Regards
Wu Zhenyu
Previous: brian m. carlsonNext: brian m. carlson
Message 3 of 5 in “Can git send-email support neomutt?”
  1. Wu ZhenyuNov 5, 2022
  2. brian m. carlsonNov 5, 2022
  3. Wu ZhenyuNov 6, 2022
  4. brian m. carlsonNov 6, 2022
  5. Wu ZhenyuNov 6, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.