On 10/10/2014 11:57 AM, Uli Schlachter wrote:
How about io.popen()? I don't have Xdialog, but hopefully this represents its behavior:

> return io.popen("(exit 1) && echo yes"):read("*a")

> return io.popen("(exit 0) && echo yes"):read("*a")
yes

This assumes that Xdialog creates an override_redirect window. While Xdialog is running, awesome will freeze and stop doing anything until Xdialog exits. This is also what would happen with your posix.wait().
Ah, I see... That freezing looks like bad idea. :) So perhaps I should code whole logic block into script like in this example and let awesome continue working on its own after spawning that script. And later - e.g. if my dialog is about manipulating some client or other awesome object - use awesome-client to interact back, keeping track of manipulated object by storing it temporarily into some table and passing its key in command line arg.

Thanks!
-- 
Best regards,
Dmitry Grigoriev


-- 
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.

Reply via email to