On Wed, 30 Oct 2019 15:49:05 -0500
Derek Martin <inva...@pizzashack.org> wrote:

> On Wed, Oct 30, 2019 at 11:31:21AM +0000, John Long wrote:
> > That doesn't really help. From my point the issue is not only what I
> > have to configure or what can be configured, but also how much code
> > is behind doing that. Less code is easier to manage than more code.
> > I can't see the benefit of junking up mutt with HTML or anything
> > else that is out of scope for a command-line mail client. Remember,
> > some of us use mutt on a console with no GUI....  
> Who is harmed more?  Users who have the feature but don't want it, or
> users who need the feature but can't get it?

That doesn't fall into the category of harmed. I'm not sure of the
timing but I believe in most cases people chose to use mutt after HTML
email was already in common (ab)use.

And I would venture to say that virtually all of the people who use
mutt either as their only email client or along with others, chose mutt
because of its simplicity. It seems to be contrary to the direction and
purpose of mutt to make it do everything anybody wants.

The harm of making the app more complicated and adding a lot of code is
real, and it directly affects the user of mutt whether he's new or old.


Reply via email to