At 11:41 PM 7/19/97 -0400, you wrote:
>On Sat, 19 Jul 1997, Carter Bond wrote:
>> Problem #2:
>> "Getting TheNextLevel to work with fvwm2"
>>
>> Fvwm95 was interesting for about 10 minutes. But I'm want a more
>> traditional X-windows look, specifically fvwm2. But I also want the great
>> features of TheNextLevel. This shouldn't be a problem, because TheNextLevel
>> works with fvwm2(theoretically). I have re-written the above .Xclients
file:
>>
>> -------------------------------------------
>> #!/bin/bash
>>
>> if [ -n "$RCFILE" ]; then
>> FVWMOPTIONS="-f 'FvwmM4 -debug $RCFILE'"
> ^^^^
>change this to -cmd
>
>This was a mistake that hasn't been fixed in the man pages yet... The -cmd
>option should be used to invoke commands or modules from the command line.
>
Are you sure about this? It works for fvwm95-2, its only when I change it
to fvwm2 that the problems occure. Also, that runs contrary to the comments
in the .fvwm2rc.m4 file:
# $Id: .fvwm2rc.m4,v 1.50 1996/06/13 21:28:09 gjb Exp $
# Resource file for version >=2.0.42 of FVWM,
# the F? Virtual Window Manager
#
# .fvwm2rc
# (C)1996 By Greg J. Badros <gjb_at_cs.duke.edu>
# You may use this file as specified under the GNU
# public license (GPL).
# I am not responsible for this file's use, misuse, or anything.
# Use at your own risk.
#
# NOTE: This must be preprocessed w/m4
# use: fvwm95 -f "FvwmM4 -debug .fvwm2rc"
#
# You may choose to grab the post-processed file, and use it
# as your permanent .fvwm2rc file. If you give the -debug option
# to FvwmM4, /tmp/fvwmrc* will have the file-- just cp it to ~/.fvwm2rc
# and you're all set. You'll of course lose the fvwm2rc's ability to
# dynamically change options based on the machine or its configurarion
#
# Generally, I'd just let FvwmM4 parse this each time-- it's not a
# huge hit on a personal machine, since you hopefully aren't starting
# and restarting X all that much... you may want to temporarily use
# the static /tmp/fvwmrc* file while playing with configurations
# or if you're having problems. It's always a good place to look to
# figure out problems with the settings.
#
#
# This should be run with something like:
# exec fvwm2 -f "FvwmM4 -debug .fvwm2rc.m4" -display :0 > .FVWM2-errors 2>&1
# in your .xinitrc file
#
# It is very helpful to use "tail -f .FVWM2-errors" to see what's happening,
# and what errors occured
--
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 Sat Jul 19 1997 - 22:57:11 BST