Comments on: Cmd.Exe and Which http://jrwren.wrenfam.com/blog/2008/01/27/cmdexe-and-which/ babblings of a computer loving fool Fri, 16 Jul 2010 11:52:58 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: jrwren http://jrwren.wrenfam.com/blog/2008/01/27/cmdexe-and-which/comment-page-1/#comment-30380 jrwren Wed, 30 Jan 2008 20:15:03 +0000 http://jrwren.wrenfam.com/blog/2008/01/27/cmdexe-and-which/#comment-30380 Yes, MS is pretty confused when it comes to cmd.exe and what it wants to allow with .bat and .cmd files. Case in point, look at the vcvars group of .bat files which comes with Visual Studio. They are buggy and actually don't work! under certain cases. between cmd, wsh, and PowerShell there is no clear path. I guess powershell is the clear path, but it isn't installed on all windows, so WSH is today's Lowest Common Denominator. I'm not sure why to pick cmd over WSH except for maybe that WSH/Cscript doesn't easily allow for calling other cmd/wsh programs. It is more like perl or python and calling execve. Oh well. I am just glad to have cygwin. Yes, MS is pretty confused when it comes to cmd.exe and what it wants to allow with .bat and .cmd files.

Case in point, look at the vcvars group of .bat files which comes with Visual Studio. They are buggy and actually don’t work! under certain cases.

between cmd, wsh, and PowerShell there is no clear path. I guess powershell is the clear path, but it isn’t installed on all windows, so WSH is today’s Lowest Common Denominator.

I’m not sure why to pick cmd over WSH except for maybe that WSH/Cscript doesn’t easily allow for calling other cmd/wsh programs. It is more like perl or python and calling execve.

Oh well. I am just glad to have cygwin.

]]> By: Collin http://jrwren.wrenfam.com/blog/2008/01/27/cmdexe-and-which/comment-page-1/#comment-30363 Collin Tue, 29 Jan 2008 21:29:42 +0000 http://jrwren.wrenfam.com/blog/2008/01/27/cmdexe-and-which/#comment-30363 Slight change: change the echo to @echo and it won't print the "echo foo" line when you run it :) Slight change: change the echo to @echo and it won’t print the “echo foo” line when you run it :)

]]> By: Catherine Devlin http://jrwren.wrenfam.com/blog/2008/01/27/cmdexe-and-which/comment-page-1/#comment-30343 Catherine Devlin Mon, 28 Jan 2008 03:10:53 +0000 http://jrwren.wrenfam.com/blog/2008/01/27/cmdexe-and-which/#comment-30343 Nice, thank you! I've long thought that so many of *nix's standbys would be very easy to implement under cmd.exe or anywhere else, so why hasn't MS done so? It seems like pure not-invented-here snottiness. (Cygwin, of course, is the ultimate solution, but why should it be necessary?) Nice, thank you!

I’ve long thought that so many of *nix’s standbys would be very easy to implement under cmd.exe or anywhere else, so why hasn’t MS done so?
It seems like pure not-invented-here snottiness.

(Cygwin, of course, is the ultimate solution, but why should it be necessary?)

]]>