> Actually in the man page should have SetEnv [...]
> not sure if this will do what you want for FvwmConsole but it will
> let you set an environment variable.
Damn. That's what I get for printing out the manual rather than
reading it online and being able to C-s it. This solved two of my
problems. I defined the following:
AddToFunc doFvwmConsole "I" SetEnv {HOME} /tmp/.dsg
+ "I" FvwmConsole
+ "I" SetEnv {HOME} HOME
(You can see I use FvwmM4 with {} specified for quote chars) Which
does the right thing with respect to running FvwmConsole and as a side
effect by changing my warp-or-run calls from
"warp-or-run FvwmConsole Module FvwmConsole" to
"warp-or-run FvwmConsole doFvwmConsole
I no longer have the problem with $3 being passed to xterm as an
argument. I still think that might be a problem for other things
though I haven't run into them yet.
On another note, now that I've got FvwmConsole working I've been able
to debug a bit. It seems that my FvwmForms are working after all. It
was my trying to get at it via calls to warp-or-run. For now I've
just made explict calls to FvwmForm. I'm guessing it's some sort of
quoting problem.
Thanks!
--
Dave Goldberg
Post: The Mitre Corporation\MS B325\202 Burlington Rd.\Bedford, MA 01730
Phone: 781-271-3887
Email: dsg_at_mitre.org
--
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 Thu May 20 1999 - 13:20:08 BST