Talk:Redirection (computing)

Hoinkies[edit]

I don't see any evidence that this is common in computing. http://en.wikipedia.org/wiki/Talk:Bracket#Hoinkies Salvar (talk) 18:39, 23 March 2009 (UTC)[reply]

Test Program[edit]

You can test all kind of redirection with this little shell script:

 #!/bin/bash
 echo "This is stdout."
 echo "This is stderr." >&2

piping[edit]

Is piping redirection? DG12 (talk) 17:01, 14 November 2011 (UTC)[reply]

Yes it is. Output from the first program is no longer going to the terminal, and input from the second program no longer comes from the terminal. —EncMstr (talk) 17:14, 14 November 2011 (UTC)[reply]

Bad analogue, someone with good English skills should rewrite[edit]

In the article

command1 | command2

was said to be equal to

command1 > tempfile
command2 < tempfile
rm tempfile

which it isn't, since the commands are executed in different subshells when a pipe is used, which means that the commands is usually executed in parallel and there is usually no temporary files created (or swap space used), just a file handle and a (usually) tiny buffer. Piping usually use much less memory then creating a temporary file and is faster. I'm guessing this is an old DOSism (in early MS/PC DOS was the given analogue correct). I'm not good enough with English to provide a better explanation, so I have only changed the wording from the two examples being "equal" to being "similar". But the analogue is still bad and might confuse someone. — Preceding unsigned comment added by Se mj (talk • contribs) 23:10, 1 December 2011 (UTC)[reply]

Done. 92.231.92.54 (talk) 14:24, 9 February 2012 (UTC)[reply]

Speaking of redirection...[edit]

I/O redirection and IO redirection should both probably link to this article. 75.139.254.117 (talk) 22:19, 11 December 2016 (UTC)[reply]

Bad examples[edit]

The article talks about a non-POSIX version of a command is as follows:

command > file 2>&1

But then a few lines down uses the exact same syntax to describe how to write both stdout and stderr to a file. The correct syntax is already mentioned on the page as:

command &>file

(I accept that the example is trying to show what is wrong with the command below, but it feels like the examples need re-writing):

command 2>&1 > file

Also, there's no mention of &>> (append) — Preceding unsigned comment added by 81.102.16.137 (talk) 16:38, 18 August 2018 (UTC)[reply]

Title[edit]

There are lot of "redirects" inside any modern OS. Perhaps a move to "Input-output redirect" should be considered. Викидим (talk) 20:14, 25 April 2024 (UTC)[reply]