X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <943be0b10803192227ibab3bbbmf1161ffb14f10557@mail.gmail.com>
Date: Wed, 19 Mar 2008 19:27:48 -1000
From: "Dave Burns" <tburns AT hawaii DOT edu>
To: cygwin AT cygwin DOT com
Subject: Re: invoke vbscript from cygwin?
In-Reply-To: <47E1A685.B9A089E8@dessent.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <943be0b10803191523g2bba03cck7e17832dc56958ca AT mail DOT gmail DOT com> 	 <23fce8e60803191549u7c26de6bo2d41e95aa9a419ae AT mail DOT gmail DOT com> 	 <943be0b10803191618u7668057cmf142fd2bd15359f2 AT mail DOT gmail DOT com> 	 <47E1A685 DOT B9A089E8 AT dessent DOT net>
X-Google-Sender-Auth: fd104ab76ac94064
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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 Wed, Mar 19, 2008 at 1:49 PM, Brian Dessent <brian AT dessent DOT net> wrote:
> 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?

That's my point. Previous poster seemed to think it should be obvious,
but I was just skimming the cygwin docs, which have no reason to
mention them.

>  The Windows Script Host is
>  documented by MS on MSDN though:
>  <http://msdn2.microsoft.com/en-us/library/ey73d9d3(VS.85).aspx>

What's that? If we'd never had this conversation, I'd never have
followed that link as a clue to solve this problem.

>  > 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.


This is useful to know. It seems non-obvious to me, as a newbie-ish
user of cygwin. Maybe I was just having brain-hiccup. Not clear where
to put it in the docs, if someone wanted to make it more obvious.
Maybe it is obvious enough already.

Short review - to run a script from cygwin, find the exe that is the
interpreter of the script (in the case of vb script, cscript.exe or
wscript.exe) and invoke the interpreter with the script as an
argument.

Thanks all,

Dave

--
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/