Hi, Albrecht
I'm sorry for forgetting to reply as you repeated in your response to
Craig.
Actually I came back very late saturday night (sunday morning at 4:00!?
:-) so I temporised my report and after that I forgot, for the good
reason that I took in reuse the version of FvwmAuto from 2.0.43, as
compiled inthere.
I spoke with Criag Sunday night, when I thought you're offline. And I
told to him what I intended to say to you too: the syntax rearranging
hasn't any effect. I almost knew it before to try it. I use Linux
2.0.27 with gcc & g++ 2.7.2.1, libg++ 2.7.1.4 and libc 5.3.12. So I
was confident. But, as I told to Craig, I suspect the problem isn't
really in FvwmAuto. Why I think that? Because FOR THE VERY FIRST TIME
it functions. I raises the first window it enters AFTER the imposed
delay.
After that, I think the variable which holds the value which is passed
to &delay in the command-line parsing part of FvwmAuto is NULL-ed. I
can't imagine how and why. But I imagine this is in fvwm.
Unfortunately I haven't enough time to pass fvwm under tests (right
now, when I write this, I'm meantime fighting with a monster FEM
library reconfiguration).
Of course the easiest workaround is to take the FvwmAuto from the
previous version and to use it with 2.0.44. This works seamlessly.
I have to sign off now.
Bye and have a lot of luck. Bonne santé
Friendly yours, Cristian
--
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 Tue Jan 21 1997 - 10:15:47 GMT