> That's why we wrote a script that converts 2.2.x configs into
> 2.4.x configs:
>
> utils/fvwm24_convert
>
> In the source distribution.
Thanks! I'm glad guys like you and Dan are working on fvwm2.
That helped a bit.
> > If you can offer suggestions on the following points, please do:
> > 1) FvwmButtons doesn't want to stay put like the FvwmTaskbar does. I
> > coulda sworn both used to...
>
> What does it do instead? And what are the responsible lines of
> your config file?
It lets me grab it and drag it around wherever I want. I want it to snap
back into position when I let it go, like the FvwmTaskBar does.
As for the responsible lines, well...
Since my dot file is pieced together from various sources, I never quite
learned exactly how every little part worked.
I believe these are the relevant lines:
Style "FvwmButtons" NoTitle, NoHandles, Sticky, WindowListSkip,BorderWidth 5
#------------------ FvwmButtons (from 2.0.42)
*FvwmButtonsFore Black
*FvwmButtonsBack #c0c0c0
*FvwmButtonsFont -adobe-helvetica-bold-r-*-*-10-*-*-*-*-*-*-*
# Geometry - really likes to pick its own size, but giving a position is OK
*FvwmButtonsGeometry -5-34
# Layout: specify rows or columns, not both
*FvwmButtonsRows 1
# Pixmap on buttons to match marble GTK theme, tinted to match wallpaper
# - MDM
*FvwmButtonsPixmap lav_marble.xpm
> > 2) I get an error message when I start fvwm2. It says,
> > "[FVWM][ParseBinding]: <<ERROR>> No such key: Help"
> > I echo its sentiment. Help? Must be some old junk somewhere in my dot
> > file, but I am having no luck finding it.
>
> Just ignore that message.
Okay...
I hate to see error messages pile up with no resolution, but I guess I'll
have to live with it (for now).
> > 4) I have to type in ctrl-alt-F1 to view error messages like that and
> > ctrl-alt-F7 to get back to X. Is there a way I can have it spit stuff
> > like that out to a nice little term on my desktop instead? I hate it when
> > stuff goes on behind my back and I don't notice those nasty little errors
> > piling up back there until it's too late...
>
> Well, starting a console should be part of your config file. I
> myself start X with
>
> $ startx 2>&1 | tee $HOME/.X.err
>
> And then run an xterm with
>
> Exec xterm -T XMessages -e tail -f $HOME/.X.err
That didn't work out for me.
Using startx with that line gave me "Ambiguous output redirect."
Thanks...
-Tenebrae.
--
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 Fri Dec 14 2001 - 09:07:01 GMT