Notmuch package recommends various MUAs, but if NeoMutt is installed, none of the recommended list should be
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| notmuch (Debian) |
New
|
Undecided
|
Unassigned | ||
| notmuch (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
The notmuch package recommends:
Recommends: elpa-notmuch | notmuch-vim | notmuch-mutt | alot, gnupg-agent, gpgsm
By default it will try to an MUA, and that will be elpa-notmuch if you don't have any other.
However, if you already installed NeoMutt, that also works with notmuch.
It's not the same as notmuch-mutt. (In fact, the notmuch-mutt package is unhelpful and a source of confusion if using NeoMutt, because NeoMutt has the functionality built in, and it's possible to mistakenly think you need to follow notmuch-mutt docs and update your .muttrc, but you shouldn't.)
When NeoMutt is installed, it doesn't install notmuch, because it only needs the library, libnotmuch.
That means, if NeoMutt is installed, you may later install notmuch (as I did to get `notmuch insert` and `notmuch tag` functions), and then it tries to install another MUA. Same if you install them in one command.
I think it would be proper to add neomutt to the list so this doesn't happen:
Recommends: elpa-notmuch | notmuch-vim | notmuch-mutt | alot | neomutt, gnupg-agent, gpgsm
I suggest it would be helpful, to a user wishing to try out notmuch, to put neomutt ahead of notmuch-mutt (at least), simply because notmuch-mutt is a bit clunky to use unlike the integrated notmuch in all the other MUAs in that list, but that's a policy decision so I'll stay out of that :-)
