X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Olumide <50295 AT web DOT de> Subject: Cygwin commands in the Windows command line Date: Thu, 13 Aug 2009 15:10:52 +0100 Lines: 16 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Hi - I've noticed for sometime that Cygwin commands such as "ps" and "ls" (now) work in the Windows command line (cmd), and I'm not sure if its because something extra I installed on/did to my machine. (In fact, the command "pwd", when run in the cmd, shows a Cygwin path like /cygdrive/c/Documents and Settings/my_name.) Is this as a result of tighter integration of Cygwin with cmd? Background to this question: I'm helping someone build a library whose Makefile calls Visual Studio's link command, and I find that its best to run the makefile the Visual Studio command prompt. Thanks, - Olumide -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple