Okay, personal one for sure here but I fail to see how it hurts anybody. If you add --disable-menubar to the configure run then I can't use the menubar functionality at all[1], however if it is not specifically disabled(and by default enabled) then I can use it should I wish and for people who don't enable it doesn't waste screen space. 1. And I have to remember all those mutt commands, instead of just grabbing at the menu when my memory fails me. Seriously though, this is a massive chunk of term usability in my eyes. vim menus for vim in terms, mutt menus for mutt in terms, etc. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 56411 [details, diff] mrxvt-I_love_menubar.patch"
Thanks for the report. I added menubar USE flag to enable that function. (It's not enabled by default but if you build mrxvt with --enable-everything it is built, so I suppose USE flag is better than building it unconditionally)