On 19 Apr 2002 14:09:18 +0100, Tim Phipps wrote: > > [EMAIL PROTECTED] wrote: > > > On 18 Apr 2002 13:46:21 -0600, Gregg Dameron wrote: > > > > > Bottom line - PipeRead is brilliant, indispensable - I'd like to see > > > itbe more so. > > > > My guess is that calling many shell utilities (read: many processes) is > > sometimes more expensive than one perl script doing the work. > > > > Moreover in pre-2.5.1 you may embed perl in fvwmrc without any additional > > processes to be called at all. You should only start FvwmPerl once and do > > 'SendToModule FvwmPerl eval perl-code' as many times as you want. > > Does this operate synchronously? One of the main reasons I use PipeRead > is to do maths in fvwm functions i.e.: > > PipeRead "bash -c 'echo some_fvwm_function $(($w * 10))'" > which will call some function with the windowid times 10. If FvwmPerl > could do this it would be very useful to me
It is not synchronous currently. Sometimes you may like to do the work in parallel with fvwm. I will solve this problem, but I want to do it in the perl library, so it may take some time to do this properly. Also, I see at least 5 different ways to specify this in the FvwmPerl syntax (using new messages, config options, command line options, perl functions in "eval" to turn synchronization on and off dynamically). > (even though I'd have to learn perl first :-\ ) I learned it 7 years ago using man pages. You may start with perlsyn(1), perlop(1), perldata(1) and then continue with perlfunc(1), perlvar(1), perlmod(1) and other 150 supplied man pages. :) And of course, one of the ways to learn perl is to patch FvwmPerl. Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
