On 21 Apr 2003 22:30:50 +0200, Felix E. Klee wrote:
>
> On Monday 21 April 2003 03:25, Mikhael Goikhman wrote:
> > > > FvwmPerl may also be used as a more powerful replacement for FvwmCpp
> > > > and FvwmM4 using its -p (--preprocess) flag.
> > >
> > > To be honest, I don't like that preprocessing stuff. Some standard FVWM
> > > expressions do always collide with the preprocessor.
> >
> > This is not the case with "FvwmPerl -p", there are no such collisions.
> > Try it just for fun. :) Here are several random ideas for preprocessing:
>
> Hm, I cannot get preprocessing to work. Here are the relevant lines from my
> .xinitrc:
>
> WINDOWMANAGER='/home/felix/local/bin/fvwm -cmd "Module FvwmPerl -p
> /home/felix/.fvwm2rc"'
> exec $WINDOWMANAGER 2> ~/local/var/log/windowmanager.log
This command looses the meaning of double quotes, so it becomes
-cmd '"Module'.
Try:
eval $WINDOWMANAGER
No, "exec eval" does not work, contact your shell documentation for more.
I would suggest to name your configuration file differently, so you know
what type of file you have, say $HOME/.fvwm/config.ppp.
> But when starting FVWM I always get
>
> [FVWM][__execute_function]: <<ERROR>> No such command '%{'
> [FVWM][__execute_function]: <<ERROR>> No such command '}%'
>
> BTW, could you add a section in the FvwmPerl man page that describes the
> configuratin neccessary for preprocessing and possibly more (sorry if it's
> already there, but I couldn't find it). This would simplify things a lot
> for beginners like me.
OK.
> Another question: When I restart FVWM with Restart is .fvwm2rc then
> repreprocessed?
With "Restart", yes.
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 Mon Apr 21 2003 - 16:22:46 BST