X-Spam-Check-By: sourceware.org Message-ID: <97f280ea0707300856m22358d2dp9bbf103268d2c1e8@mail.gmail.com> Date: Mon, 30 Jul 2007 18:56:08 +0300 From: "Amir E. Aharoni" To: cygwin AT cygwin DOT com Subject: Re: windows cmd Newb question In-Reply-To: <11865792.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <11865792 DOT post AT talk DOT nabble DOT com> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 30/07/07, zip184 wrote: > Cygwin commands are not working when I run them in windows cmd.exe. Should > they? Commands that are exe files are supposed to work. For example perl and grep are both exe files in your bin directory, which is something like C:\Cygwin\bin in Windows terms. If you have that directory in your path, then those commands will work from a regular Windows cmd shell (a "DOS Window"). Anything else is not supposed to work. Commands which are not exe files, for example shell scripts (bash, ksh, etc.) or Perl or Python programs will not work directly from the cmd command line. You need to invoke their interpreter first. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/