| |||||||||||||
Evolution of shells in Linux (developerWorks)Evolution of shells in Linux (developerWorks)Posted Dec 8, 2011 20:41 UTC (Thu) by ccchips (guest, #3222)In reply to: Evolution of shells in Linux (developerWorks) by Cyberax Parent article: Evolution of shells in Linux (developerWorks)
I need the equivalent of:
foo >bar 2>&1
to have *every* text line from standard output and *every* error line that would sho up in red on the screen, as the result of the above command.
(Log in to post comments)
Evolution of shells in Linux (developerWorks) Posted Dec 8, 2011 20:58 UTC (Thu) by Cyberax (✭ supporter ✭, #52523) [Link]
You'd be surprised, but the equivalent of "foo >bar 2>&1" in PowerShell is:
> foo >bar 2>&1
Yep. It works just as in Unix.
Evolution of shells in Linux (developerWorks) Posted Dec 8, 2011 20:59 UTC (Thu) by ccchips (guest, #3222) [Link]
Ok, well I just tried "2>&1" on that job and it worked. Stupid me. I was looking for instructions rather than experimenting.
However, I did find a different problem; things go really wrong if you try something like this:
dir | get-content
because "get-content" takes a list of objects from the input pipe that are interpreted as file names.
Still, my first problem is solved, I have egg on my face, and so it goes. I never said I didn't like Powershell--I enjoy working with all of the common shells (except maybe MS-DOS Command prompt) and would like to see Powershell be more easily integrated with existing tools.
I suspect there is a way to get "dir | get-content" to act more like UNIX shells would, but we could argue all day about the merits.
|
|||||||||||||