Mikhael,
Actually, when I said run another fvwm I was thinking of the '-replace'
option. That did work. I reran it without using '-C TrueColor', and
here's what PrintInfo Colors gives me.
FVWM info on colors
Visual ID: 0x20, Default?: Yes, Class: PseudoColor
Depth: 8, Number of colors: 256
Pallet with 64 colors, Number of free colors: 0
Auto Detected: Yes, Strict: No, Allocated: Yes, Dynamic: No
Number of colours used by fvwm:
In the table: 64
Out of the table: 9
Total: 73
So by default, it seems fvwm is grabbing 8-bit color mode. When I use
'-C TrueColor' it seems to be running correctly as far as color (though
I should probably get the PrintInfo Colors info for this too), but
that's when I start having the FvwmTaskBar issues.
Thanks,
Ben
>If (and only if) fvwm is not the last xinit program running in the
>foreground you may replace it with another fvwm that you run from any
>xterm using: "fvwm -replace >& fvwm.out" (with some shells you need
>to do "> fvwm.out 2>&1". Otherwise you may quit X by doing this.
>
>Another way that should always work is to issue "Restart xterm" from
>FvwmConsole or menus. Then when you get xterm and no decorations (since no
>window manager is run), you may start fvwm inside this xterm by executing
>"fvwm" with optional stdout/stderr redirection. Just remember to close
>this xterm to close your X session with some X setups.
>
>Regards,
>Mikhael.
>
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Wed Dec 18 2002 - 20:17:36 GMT