On 22 Apr 2003 19:51:29 +0200, Felix E. Klee wrote:
>
> On Tuesday 22 April 2003 16:49, Mikhael Goikhman wrote:
> > I thought I explained in the parent message why it should be:
> >
> > AddToFunc StartFunction
> > + I ModuleSynchronous FvwmPerl
> > + I . Module FvwmPager 0 %{ 5 }%
>
> Thanks, now it works.
>
> > Or, maybe it does not work for you because you changed the quote char
> > using preprocess({ 'command' => 1, quote' => '*' }, q<$*>).
>
> No, I didn't redefine the quote character. I have disabled preprocessing of
> the whole configuration file. The problem is that variables defined during
> this kind of preprocessing aren't available later for use with the "."
> command.
Actually it is possible to tell the FvwmPerl that preprocesses the whole
configuration to stay with fvwm, so all variables are still available.
Then use %{}% for statical preprocessing and *{}* for dynamical.
For example, create .fvwm2rc with only one line:
ModuleSynchronous FvwmPerl --preprocess config.ppp --stay
But I should check up all synchronization issues with this.
> Therefore I moved all intitialization to init functions that are
> called from StartFunction. This works very good and AFAICS I don't need
> preprocessing of the whole config file anymore.
>
> Some comments:
> 1. "." is very cool. Now that everything seems to work fine, please add it
> to the FAQ. And, as said before, include one or two simple examples that
> show that "." is usable with minimal Perl knowledge (eg. for adding
> variables).
Later, when 2.5.7 is out.
> 2. It seems that with "." it is only possible to embed one Perl command in
> %{ ... }% at a time (i.e. not several Perl commands separated by ';').
> That should be made clear in the FAQ.
What is the problem with 2 or 10 commands? Works fine for me (prints 3):
. Exec exec xmessage %{ $count = 1; $count++; $count + 1 }%
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 [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
