Git Mailing List Archive mirror
 help / color / mirror / Atom feed
From: Wu Zhenyu <wuzhenyu@ustc.edu>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org
Subject: Re: Can git send-email support neomutt?
Date: Sun, 6 Nov 2022 17:02:33 +0800	[thread overview]
Message-ID: <20221106090233.ukf6rjzrygpnavzh@desktop> (raw)
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:
> 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


  reply	other threads:[~2022-11-06  9:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-05 15:46 Can git send-email support neomutt? Wu Zhenyu
2022-11-05 18:10 ` brian m. carlson
2022-11-06  9:02   ` Wu Zhenyu [this message]
     [not found]   ` <20221106085820.m53mwajd5yfsyri4@desktop>
2022-11-06  9:14     ` brian m. carlson
2022-11-06 10:17       ` Wu Zhenyu

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=20221106090233.ukf6rjzrygpnavzh@desktop \
    --to=wuzhenyu@ustc.edu \
    --cc=git@vger.kernel.org \
    --cc=sandals@crustytoothpaste.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 read-only IMAP folder(s) and NNTP newsgroup(s).