The xterm ebuilds all supply the --disable-toolbar option to configure. This prevents getting the new menu bar feature. If adding --enable-toolbar prevents xterm from working, can you please add a comment to the ebuild explaining that so that I won't complain? Otherwise, if --enable-toolbar works, can you please switch to that? Note that compiling with --enable-toolbar does not force people to have menu bars. The presence or absence of a menu bar can still be selected when xterm is started with X resources and can also be toggled at run-time with key bindings and escape sequences. Reproducible: Always Steps to Reproduce: 1. 2. 3.
As far as I know, the only issue with the toolbar is that it cannot be properly enabled after startup (a geometry bug). But the resource for disabling it, and the escape sequence for disabling it work. So it should be safe to add (though not everyone would like it).
xterm-200 is making its way into portage right now. The local use flag "toolbar" will be used to enable and disable the toolbar, at your request. Please test.
The toolbar seems to work fine in x11-terms/xterm-200 when this ebuild is merged with "toolbar" turned on. I can toggle the toolbar on and off with the menu item. However, for some reason, all my X resource settings are being ignored. When I re-emerge with "toolbar" off, I get an xterm that pays attention to my X resources. My X resources for xterm look like this (output of "xrdb -query | grep -i xterm"): XTerm.VT100.font: 9x19 XTerm.VT100.WideChars: true XTerm.VT100.FaceName: Courier New-8 XTerm.VT100.EightBitInput: false XTerm.VT100.saveLines: 5000 XTerm.VT100.backarrowKey: true XTerm.VT100.translations: #override XTerm.VT100.Geometry: 100x39 XTerm.VT100.CutNewline: false I'm guessing that somehow enabling the toolbar is changing the class name xterm uses when looking for resources. Or maybe it is changing the widget name. Any idea why? I don't know whether to reopen this bug or enter a new bug. Please advise.
I suspect my problem with X resources is that there must now be an additional widget between the application shell and the VT100 widget. I'll check if this is the case later today and report back.
I can now verify that my resource problem is caused by the vt100 widget being at a new location in the widget tree: xterm.form.vt100. So everything works with the new toolbar feature except that I can't figure out how to prevent xterm from starting up with the toolbar showing. Instead, I have to hide the toolbar manually using the menu or an escape sequence. Despite the comments above, I could not find any X resource that governs this either in the documentation or in the code. If anyone knows how to do this I would be happy to be proven wrong.
I know someone who might have an idea ... =)