From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Wu Zhenyu <wuzhenyu@ustc.edu>
Cc: git@vger.kernel.org
Subject: Re: Can git send-email support neomutt?
Date: Sat, 5 Nov 2022 18:10:10 +0000 [thread overview]
Message-ID: <Y2anAijZxu9QEX4M@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <20221105154600.hbrqs74inmvpebie@desktop>
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2022-11-05 18:10 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 [this message]
2022-11-06 9:02 ` Wu Zhenyu
[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=Y2anAijZxu9QEX4M@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=wuzhenyu@ustc.edu \
/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).