Dumb Questions: Why Is Threading Not Enabled In Repo Version of mutt, Et Al?

,

Hey All,

I tried a search before posting this, but due to having the application name so similar to our favorite compositor, well, it just wasn’t very fruitful. So…

I am a long-time and pretty much a daily user of the terminal-based email MUA, mutt, and I do find that every once in a while, it’d be great to toggle threading on temporarily. But, since that compile-time switch has been disabled I cannot do that.

Is there a technical reason why this is the case? How would I best go about asking that this be changed if there wasn’t such a reason? Can I contact the package maintainer directly, or is it considered uncool to do that out of the blue?

Finally, while I’m at it with questions related to mutt: Is there a reason why the move from f38 to f39 involved downgrading it from 2.2.12 to 2.2.10?

And, yes, I’m well aware that I am free to download the app source and compile/link it myself. I went down that path while being constrained to older versions of RHEL for many years at my former employers, but to install it as a simple user application, I would have to put a bunch of symbolic links to make sure all the accompanying up to date resources are found, and I’d just prefer not to take that on as bookkeeping task if at all possible.

Many thanks!

What switch is that? I couldn’t find one in a cursory search.


Regarding the version in F39, mutt is getting updated in Rawhide and F38, but not F39. That seems like an oversight. I think it would be worth filing a bug.

You can see the package source here: https://src.fedoraproject.org/rpms/mutt

It is enabled by a config switch, and, as it turns out it is enabled in the repo version. I just re-learned that you have to invoke it via the sort variable. The re-discoveries just keep making life interesting… :slight_smile:

Oh, and on the version number, I just brought that up because f38 already had been updated to 2.2.12 before I system-upgraded to f39 a week ago. During that process that application got downgraded back to 2.2.10.

Thanks for your reply!