How to stop Mutt from prompting for Subject
When I want to compose a new email, Mutt will prompt for the recipients
("To:"), followed by the subject ("Subject:"). How do I disable the
prompting for the subject? The `autoedit` configuration option will not
help here because it disables both prompts (i.e. both "To:" and
"Subject:"). I only want to disable the "Subject:" prompt. How can I do
this in Mutt?
How to warn before sending email if "Subject:" is empty
Is it possible to make Mutt warn about an empty "Subject:" right before sending the email? The `abort_nosubject` configuration variable is not relevant here because `abort_nosubject` is only for configuring what happens when there is no subject given at the subject prompt. I am looking for something similar to `abort_noattach`'s "No attachments, cancel sending?" warning that appears right before email is sent. Is there something similar for warning about an empty "Subject:"?
Re: NeoMutt Opinions
On 23-12-2021 00:50:24, Oleg A. Mamontov wrote: > On Wed, Dec 22, 2021 at 01:02:11PM -0800, Lee K wrote: > > I was wondering if anyone has an opinion on the neomutt project. I've > > been a long time mutt user, on and off for 15 years. Neomutt seems to be > > popular with a certain set of users these days. The configs seem pretty much > > compatible. I haven't seen any features that aren't in mutt, and it's sole > > virtue seems to be a more colorful site page. > > The feature of neomutt that completely determines my choice is an > elegant built-in integration with notmuch. Really worth to try. Yep, same here. notmuch is pure gold! (I'm syncing between my server and my devices with muchsync, which is another valuable tool in the chain - no need for mbsync/offlineimap or whatever). I fear the days where my dayjob requires me to use something else (than neo/mutt). -- Matthias signature.asc Description: PGP signature
Re: NeoMutt Opinions
On Wed, 22 Dec 2021, at 22:50, Oleg A. Mamontov wrote:
> The feature of neomutt that completely determines my choice is an
> elegant built-in integration with notmuch. Really worth to try.
Like Oleg I see the notmuch integration including the notmuch:// protocol for
folders as the biggest selling point of notmuch these days plus the Lua
scripting interface.
That being said, while I could see myself not being able to do without that
much notmuch in a business setting where mutt would be front and center of my
emailing and day-to-day work; for my private use, mutt is enough --- I use
notmuch mainly for search across mailboxes and detailed search, and for that,
these trusty macros have been in my muttrc for years unchanged and do the job:
macro generic,index,pager \
"mbsync -aqnotmuch new" "fetch mail"
macro index \
"set my_old_pipe_decode=\$pipe_decode
my_old_wait_key=\$wait_key nopipe_decode nowait_key\
notmuch-mutt -r --prompt search\
`echo
${XDG_CACHE_HOME:-$HOME/.cache}/notmuch/mutt/results`\
set pipe_decode=\$my_old_pipe_decode
wait_key=\$my_old_wait_key" \
"notmuch: search mail"
macro index \
"set my_old_pipe_decode=\$pipe_decode
my_old_wait_key=\$wait_key nopipe_decode nowait_key\
notmuch-mutt -r thread\
`echo
${XDG_CACHE_HOME:-$HOME/.cache}/notmuch/mutt/results`\
set pipe_decode=\$my_old_pipe_decode
wait_key=\$my_old_wait_key" \
"notmuch: reconstruct thread"
Most of my email processing these days is also happening server-side (starting
from SPF, DKIM, DMARC, ARC and ending at Sieve) so that I simply do not need
turing-complete script bindings via Lua in my MUA. This used to be different
(msmtp > procmail > (filter chain) > mailbox, but not anymore.
