Linked by Eugenia Loli-Queru on Mon 24th Oct 2005 04:14 UTC, submitted by Eric
Ars Technica has posted a lengthy article on the new promising Microsoft Command Shell. It looks at MSH from the point of view of both coders and Windows admins.
Thread beginning with comment 50488
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-06-29
Yes, I'm aware of it. But for me, it'd be a hindrance as my main uses for Windows these days are:
a.) Games
b.) Porting to Windows
It messes up b because then I forget things like the lack of pthreads without SFU.
I end up installing ming though, which also gives you bash and a few development utilities. Usually ming plus emacs (when I can get it to work and don't have to use the inferior xemacs) is good enough for a lite workload.
I do know now to avoid Cygwin though, heh. If it installs, yay. If the install fails, there goes an hour of your life.
Member since:
2005-07-09
If you haven't already, consider giving Services for UNIX (SFU) a try. To me, it's one of the best, free as in beer downloads Microsoft offers. While it doesn't doesn't allow you to leverage Windows specifics (although I use VIM to write VBScript with syntax highlighting
, it will give you a very nice shell in Windows (not to mention well integrated access to standard UNIX commands). Especially after a quick visit to www.interopsystems.com. From there you can add BASH, TCSH, ZSH and/or even an OpenSSH server. Crave an X Windows Server with that? http://freedesktop.org/wiki/Xming can help with that too. SFU includes CSH and KSH. If you do a custom install, you can add a complete GNU development environment and perl as well.