Another idea. I find that MS's command.com shell is a rather poor effort - especially compared to powerful Unix shells like the Korn Shell. I think it would be really cool if we had a shell which has the best Korn Shell features, a cleaner syntax and interoperability with .NET.
For example, I should still be able to do things like invoke programs, pipe streams, and access environment variables - but in addition to that, I could instantiate, access objects and classes, call methods.
An additional possibility is the inclusion of network pipes which are like normal pipes, but are generalised to work over a network as well. I think this was pioneered by JXTA, Sun's solution to peer-to-peer programming.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It's sad to see people still think that command.com is the only shell.
command.com is a 16-bit PoS from the DOS days that is kept around only for legacy.
The fully 32-bit shell is cmd.exe which has been around since the first NT.
cmd.exe is awesome and has many features you'd expect from a modern shell.
The new batch scripting support has come a long way. It's nearly as full featured as bash scripting. The syntax is a little less than desirable, but with enough determination, you can convert just about any bash script to a BAT file.
Also, the TAB completion in cmd.exe is far superior to that of KSH (Emacs for your shell? come on!) and bash.
In bash, if you type something and hit tab, and there are more than one files/dirs that match that query, you'll just get a completely worthless beep.
In cmd.exe, it's much more helpful. It will go to the first item. If you continue to hit tab, it will cycle through the other possibilities. Also, there's shift+tab which will reverse cycle through the list.
Use cmd.exe for awhile. You'll find that it's a much easier shell to work with on a day-to-day basis than bash and definately ksh.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Another idea. I find that MS's command.com shell is a rather poor effort - especially compared to powerful Unix shells like the Korn Shell. I think it would be really cool if we had a shell which has the best Korn Shell features, a cleaner syntax and interoperability with .NET.
For example, I should still be able to do things like invoke programs, pipe streams, and access environment variables - but in addition to that, I could instantiate, access objects and classes, call methods.
An additional possibility is the inclusion of network pipes which are like normal pipes, but are generalised to work over a network as well. I think this was pioneered by JXTA, Sun's solution to peer-to-peer programming.
It's sad to see people still think that command.com is the only shell.
command.com is a 16-bit PoS from the DOS days that is kept around only for legacy.
The fully 32-bit shell is cmd.exe which has been around since the first NT.
cmd.exe is awesome and has many features you'd expect from a modern shell.
The new batch scripting support has come a long way. It's nearly as full featured as bash scripting. The syntax is a little less than desirable, but with enough determination, you can convert just about any bash script to a BAT file.
Also, the TAB completion in cmd.exe is far superior to that of KSH (Emacs for your shell? come on!) and bash.
In bash, if you type something and hit tab, and there are more than one files/dirs that match that query, you'll just get a completely worthless beep.
In cmd.exe, it's much more helpful. It will go to the first item. If you continue to hit tab, it will cycle through the other possibilities. Also, there's shift+tab which will reverse cycle through the list.
Use cmd.exe for awhile. You'll find that it's a much easier shell to work with on a day-to-day basis than bash and definately ksh.