So I dl'd and tried Windows Powershell. Apparently MS tried to clone GNU bash and got a pile of fail. Have you tried it?
Discuss.
Name:
Anonymous2007-11-03 23:46
If I absolutely had to use a Windows system, I'd use it. It can't hold a candle to almost any given Unix shell, but it still makes Windows suck a tiny bit less.
Name:
Anonymous2007-11-04 9:10
Somewhat awkward for me since I'm not fluent in .NET shit. I may toy around with it some more when I have time. Seems pretty useful for a Windows CLI.
Name:
Anonymous2007-11-04 12:57
lulz. i found the powershell owner's manual thing and it sez:
4: Piping and the Pipeline
Discover the true power of Windows PowerShell by learning about the pipeline.
Unix: The future was 37 years ago.
Name:
Anonymous2007-11-04 13:34
>>4
Well to be fair, pipelining also existed in DOS, as well as its various incarnations in Win9x and the command shell of NT-Vista.
Try 'type lol.txt | more' in one of those. Works fine.
Name:
Anonymous2007-11-04 20:38
Bash has been ported to Windows, you don't need to hurt yourself anymore.
>>7
Uh... because 'less' is a play of words with 'more' which has existed longer than 'less' but has less features. 'less' is to 'more' like 'vim' is to 'vi'. And 'less' doesn't work on Windows because it's not part of the system by default. But all that has nothing to do with my point.
Name:
Anonymous2007-11-05 15:37
Powershell is fail. So is CYGWIN. So is bash.
I'd suggest UWIN http://www.research.att.com/sw/tools/uwin/
which is a UNIX like environment for windows. Uses the KornShell which is pretty much bash with the addition of floating point arithmetic and associative arrays. WIN.
Name:
Anonymous2007-11-05 15:52
>>11
PowerShell supports floating point arithmetic too. And lambda expressions, which ksh (or bash, for that matter) doesn't.
Name:
Anonymous2007-11-05 16:16
Good thing lambda expressions have limited applicability and aren't even necessary.