> Lots of people have said xman works fine, or that there is no problem with
> it. Odd, I can start xman, get a manual page up, but thats it.
here is a couple of questions for my own curiosity.
What X resources do you have set? Some window managers (olvwm) run a
special init script or something (.openwin-init) that will setup special
X resources...
Try comparing the X resources while running fvwm to olvwm...perhaps xman
doesn't have anything bound to the menu options? I have toyed with x
resources and rendered menu options usless without understanding how...so
that would be my best guess there..
It isn't specially fvwm's fault, but the fact that window managers (ahem)
openwin, tend to do a little more cludgy X startup than just putting things
in .xinitrc where they belong...
Another question. Would those people who use xman that have problems please
mention the version?
I have xman 3.1.6, linux 2.0.0, running the latest X11R6.1 XFree86 3.1.2e
beta X server (whew!), and fvwm-2.0.42 without any problems...and since there
are others in the world who don't seem to have problems, my first hunch
is there are several X resources / environment variable differences.
Try doing an 'xrdb -merge /usr/openwin/lib/app-defaults/Xman' and see if
that does any good.
> In filemgr for example (Sun's fine File Mangler) some option menus
> just vanish behind the main window. Hard to set options then!
Hrm, what happens if you mess with click-to-focus and such for these apps? Are
you having the app itself raise when it gets focus and push-pinning the menu
to the desktop underneath the app?
Just some curiosities of my own on the matter..
--
Todd Fries .. todd_at_miango.com .. todd_at_emcee.com .. tfries_at_umr.edu
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Thu Jun 13 1996 - 22:47:08 BST