X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <47E1A685.B9A089E8@dessent.net> Date: Wed, 19 Mar 2008 16:49:25 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: invoke vbscript from cygwin? References: <943be0b10803191523g2bba03cck7e17832dc56958ca AT mail DOT gmail DOT com> <23fce8e60803191549u7c26de6bo2d41e95aa9a419ae AT mail DOT gmail DOT com> <943be0b10803191618u7668057cmf142fd2bd15359f2 AT mail DOT gmail DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com 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 Dave Burns wrote: > Yes, that worked splendidly. Should I have known about these > executables? Are they the regular interpreters for vbscripts? I know > little about cygwin and nothing about vbscript, and I did not see > these mentioned in the documentation. The Cygwin documentation? Why would they be there? We can't document every possible non-Cygwin application that someone might want to use, that would take gigabytes of space. The Windows Script Host is documented by MS on MSDN though: > Maybe I was too hasty, but I > didn't even see "Here's how you invoke a regular windows .exe from > within cygwin". I'm sorry for mystifying you - someone handed me an There's no fundamental difference between running a Cygwin command and a non-Cygwin command from a shell prompt, in the end it's just an .exe either way: you type its name and the shell runs it if it can find it in the PATH. Brian -- 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/