Quote:
Originally Posted by xyclonei
I thought using cmd_output instead of cmd_spawn so that the script has a chance to indicate when it is done might sort it out:
|
In fact I've been using cmd_spawn instead of cmd_output exactly because of this reason - the latter has a max. 10 second timeout.
But looking at the NickeMenu source code and its docs it seems to me that cmd_spawn will start detached from the main process, but a chain will only continue after the previous item has finished.
My personal experience seems to confirm this, as the dbg_toast message always took its time depending on how many new articles there were. Additionally if you look at the NickelMenu docs, you can see that e.g. the telnet process also waits for the different commands to end before going on to the next one:
https://github.com/pgaskin/NickelMen.../doc#L207-L209
I might be mistaken, but that's what I gathered so far.