Hi Derek, On Friday, 2016-08-26 17:46:09 -0500, Derek Martin wrote:
> On Fri, Aug 26, 2016 at 01:50:40AM +0200, Eike Rathke wrote: > > Alias for the configuration I meant. If both are used the last one wins. > > Simple. > > Yes, I know what you meant. Do you run Mutt because it is easy to > configure (HA!) or because it is good software? Both :-) Yes, actually I find it easy to configure, once you got how things work. > Aliases should be avoided, unless there is a very, very compelling reason > to create one. And this isn't that. Ok, your opinion, but I'm not buying that. IMHO there's no compelling reason to not keep an alias for two releases and after that remove it. > > I can't use the same configuration with different mutt versions. > > I understand, but your objection is not reasonable. Taken to > extremes, this logic means that no change can ever modify config > behavior, no matter how broken it may be. Development must not be > stunted by such an attitude. Besides, it reaks of the mentality, > "I want all the new functionality of new Mutt, but none of the > responsibility of configuring it." At the very least, I think it > should strike you that that thought process is selfish. *I* can deal with such configuration problems in one or the other way. Calling me selfish because I'm thinking of other people who may run into the same problem is a tad off the lane.. > set my_muttvers=`mutt -version |head -n 1 |sed 's/^Mutt > 1.\([0-9]\+\).*$/1.\1/'` > source .muttrc-$my_muttvers Neat idea. > > I'm using mutt since ~20 years. Config things broke rarely. > > Small wonder... between 2002 and 2015, Mutt only had TWO minor > releases. JUST THIS YEAR, we've had two. And in those two, here is > only just one more "breakage" of config, and so... still, only rarely. > > Development has picked up again. Things are changing. Get used to > it. =8^) I'm glad development has picked up again. > > > That's a fact of continued development. If you don't want old stuff > > > to break, don't run new code. > > > > Haha. Very funny. > > Hey... It's not a joke. With any software, some old features get > retired, some are improved, and configurations change accordingly. > New features means new config. Fixing old brokenness sometimes means > old config breaks, and old features don't work. Welcome to software. > Technology changes quickly and you should be prepared to change with > it. Mutt has been fairly stagnant; I think you should see the recent > increase in the rate of change as a good thing. I do. Though I don't like the attitude that new stuff has to come along with breaking old configuration, or an old configuration breaking the behavior. If we did the same in LibreOffice with each release we'd get angry bug reports all the way (we do anyway but..). Yes we sometimes let break things intentionally as well, but only if keeping compatibility is way out of maintainability. Mutt certainly has the advantage of its users being more technically savvy, so they usually can come up with some solution for their problem. Like your mutt-version dependent config above. Eike -- OpenPGP/GnuPG encrypted mail preferred in all private communication. Key "ID" 0x65632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A Better use 64-bit 0x6A6CD5B765632D3A here is why: https://evil32.com/ Care about Free Software, support the FSFE https://fsfe.org/support/?erack Use LibreOffice! https://www.libreoffice.org/
signature.asc
Description: PGP signature
