From: Simon B. <si...@cs...> - 2004-03-25 00:05:19
|
On Wed, 24 Mar 2004, Joseph Ritz wrote: > On Wed, 24 Mar 2004 17:25:55 +0200 > Jouni Tapio Rinne <jou...@lu...> wrote: > > > Hi! > > > > I'm doing some experiments with different compilation options. What > > does the option '--enable/disable-gnome' actually do? I don't see any > > difference regardless of whether it is enabled or disabled. > > > > Jouni Rinne > > > > My guess (and I emphasize the word "guess") is that with a clean > installation, enabling gnome at compilation would build a fluxbox > whose auto-generated menu would be complemented with a submenu of > Gnome menus. Compiling again without --enable-gnome may not necessarily > overwrite the previously created menu and the gnome menus may still > appear. Try a clean compilation with the --disable-gnome option, making > certain first that all remnant files have been removed or renamed, and > see if you have a package whose menu does not include the Gnome submenu > by virtue of the --disable-gnome option. (just a guess, mind you) Hi, --enable-gnome enables support for GNOME window hints. These are before the EWMH standard ones. Things like _WIN_WORKSPACE. For example, "Eterm -D 2" sets the gnome hint to open on workspace 3 (the 2 is zero indexed). Same for KDE support (though that also includes kde systray support). Personally, I don't think you gain much by turning them off - it just makes some features of some apps not work. Gnome/KDE menu support is always in fluxbox-generate_menu, but I think you have to give it flags to actually use it (-g, -k). Cheers, - Simon |