* On 05 Mar 2020, Fabian Groffen wrote: > > Right, at this point, I wasn't aware, and surely did not expect unset > options to be *a bug*.
It is unusual. But back in that day, the stock Muttrc was considered default behavior. We didn't really expect in 2002 or whatever that there would be dozens of separate packagers who each customized the defaults. To me, customizing Muttrc in a package is no different from introducing patches to change behavior. Looking over the documentation now, it might make sense to clarify this situation. > We can debate this, of course, but it seems easier to append the > necessary attachments settings of Muttrc.dist to the provided Muttrc > (based on mbox/maildir) and solve this "bug". Yeah, I don't think there's a lot of debate to be had though unless someone wants to convert these default settings to C code. At the time we implemented this, we didn't especially expect the defaults we chose then to remain preferred indefinitely, and it made sense for them to be easy to modify. Maybe now it makes sense to hard-code it. > We might have to notify others, to ensure they don't produce this "bug" > either, such as https://lukeross.github.io/MuttrcBuilder. I mean, if you know about some of these things then it would be kind of you to ping them. However I don't know about any config builders (I've never used one for any software package) and I think it's fair to consider it their responsibility to know the software they're configuring. > In any case, I'll see to this for Gentoo's next release. Awesome, thanks! -- David Champion • d...@bikeshed.us
