Talk:Execute a system command: Difference between revisions

Content added Content deleted
(→‎Korn Shell: new section)
Line 22: Line 22:
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)
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)


== Korn Shell ==
== 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)
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)