In this particular situation the problem is low-level - it is that you
are unable to anyhow interfere after you called io.popen (like interrupt
it after a timeout). That's not a bug, it's just a feature missing. But
after all the responses I understood that it's easier and more
appropriate to redesign my code than to demand such a feature in a WM.
Thanks to all of you for your help.
Regards, Alexander
On 12/11/2011 10:46 PM, Nick Demou wrote:
On Thu, Dec 8, 2011 at 3:07 PM, Alexander Yakushev
<[email protected]> wrote:
So here's my problem. I use a weather widget that fetches the data from a
shell script via io.popen. It works great while I'm connected to the
Internet but if I'm not it just freezes the entire WM.
Just a thought:
I don't know enough specifics so I can only guess you're either
hacking awesome at a low level or working at a high ("user") level. If
hacking at low level you should handle failures with caution (and the
ideas posted are good pointers -- I would've used the split approach
were network depended stuff are run in a process outside of the window
manager). But if you're working at a high level instead of hacking the
internals then it's a fault of the window manager that it's not
handling the failure of your code nicely. If that's the case you
should consider posting a bug report.
--
To unsubscribe, send mail to [email protected].
