Anonymous user
Talk:Execute a system command: Difference between revisions
→UNIX Shell Command Substitution: Fixed.
(→UNIX Shell Command Substitution: Fixed.) |
|||
| (3 intermediate revisions by 2 users not shown) | |||
Line 17:
: It's worth noting, though, that if you block your VB6 thread with WFSO, you're blocking your message processing thread, and Windows will notice your process has stopped responding (until the child process terminates). The normal resolution would likely be to have a timer trigger a WFSO(hHandle,0) at a reasonable interval. (This assumes that threaded concurrency isn't possible within VB6. If it is, I don't know how.) --[[User:Short Circuit|Michael Mol]] 14:45, 11 January 2010 (UTC)
== Task Extension ==
How about a version of this task in which you process the input in some way? Maybe get a PID from ps or find a file with a certain extension from ls? It should probably be separate from this task since it seems a lot of these just execute the command and the output is automatically directed to stdout. --[[User:Mwn3d|Mwn3d]] 20:57, 23 September 2010 (UTC)
== UNIX Shell Command Substitution ==
Odd that the UNIX Shell examples attribute the "backtick" notation [ `command` ] to the C Shell and the Korn Shell, first since it was the Korn Shell that '''introduced''' the more modern "parenthetical" notation [ $(command) ], and second since the original "backtick" notation was introduced in the Bourne Shell and then only copied by other shells such as the C Shell. --[[User:Balrog|Balrog]] 21:22, 26 February 2011 (UTC)
: Fixed. --[[User:Kernigh|Kernigh]] 23:44, 31 August 2011 (UTC)
| |||