Mutt next generation (mutt-ng) is a fork of the well-known email client mutt
with the goal to both incorporate all the patches that are floating around in
the web, and to fix all the other little annoyances of mutt. Also this port is
using options structure that is more comfortable for some people including me.
Does it worth making a port? I think we have most of these patches
in mail/mutt-devel. Personally I think project doesn't deserve to
be called "ng" just because of integrating a bunch of third-party
As for me mutt-devel dumps core when it is built with sidebar support
during switching mailboxes. Another reason is that mutt-ng is official
fork of mutt client and I think that it would include some interesting
features. But if you think that it is not worth porting there is no
problem - I'll use it for myself.
As for me, of course mutt-ng have most of these patches in mutt-devel, but if
in mutt-devel they not working OK, why we don't have a port where this pathes
work good ?
And as has told Vsevolod, the project can contain interesting decisions in the
I vote for this port :)
It's not Vsevolod decision to name project mutt-ng ;)
Say NO to bikeshed !
P.S. I would paint mutt-ng in green color
-----BEGIN PGP SIGNED MESSAGE-----
Ok, let's end that useless conversation about the color of mutt-ng.
> Mutt next generation (mutt-ng) is a fork of the well-known email client mutt
> with the goal to both incorporate all the patches that are floating around in
> the web, and to fix all the other little annoyances of mutt. Also this port is
> using options structure that is more comfortable for some people including me.
Name those "little annoyances of mutt", that mutt-ng fixes.
The new features mutt-ng introduces and why are they useful. Also
explain the situation when mutt crashes and mutt-ng does not. If this
really happens with the latest version of mutt, consider sending a PR
anyway, no matter whether mutt-ng enters /usr/ports/ or not.
1. mutt and mutt-devel do A when I expect them to do B, which I find
very annoying. This cannot be tuned via muttrc.
2. mutt-ng has this nice thing C that I use when I need to do D, this
feature cannot be found in mail/mutt/files/ nor in
3. etc. etc. etc.
Just convince us that mutt-ng really worths.
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
Here is a list of some inetersting features:
* Better view support for format=flowed attachments
* Message IDs are configurable
* User can set signoff_string just like in slrn
* User can call up the "last folder" when saving attachments
* IMAP reconnecting: when the connection to the IMAP server dies,
mutt-ng attempts reconnecting
* User can set the umask with which all the files shall be created
(was hard-coded before, and caused huge problems for shared
mailboxes to some people)
And here is changed version of port that fixes building under CURRENT and
also some dependencies and plist fixes.
New port added, thanks!