X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:references
	:mime-version:content-type:in-reply-to; q=dns; s=default; b=PbPv
	R8bkzqTaDNU+P4+yZGbQtXmW+E56OVj0BSEdvQPct+VY4UEeEc6uGZipT64N9GPu
	KnqpRZRg8M0wNSkbhIH6O+G71dgJA+gNRs37VG2EimDXJ39Vp9LSaRIbvGRUIWt1
	aBgXOZapjmKTaWScijK/5dBDasiyQgLpelzuJpo=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:references
	:mime-version:content-type:in-reply-to; s=default; bh=dpfDKwagb8
	cxfacvv+aPlyJKS6M=; b=m3uudy7A34IOe5dv/bfWzCJqS673c2+LcfcAzBD/Cq
	q21MXVCHpTRChEFFgKf6z2RGQfGwYLk391dNP6njRUxzHp1p7iy1Jtr0J0Sq8j0M
	nxnHlxp74QNl/IW5hxdtLTyu3WY87BPBugGbdeHzfzu+YK0iaDr4N/IvFATlRC0J
	Q=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-2.8 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail.spocom.com
Date:	Mon, 8 Sep 2014 12:09:41 -0700
From:	Gary Johnson <garyjohn AT spocom DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: latest cygwin: 'run' problem
Message-ID:	<20140908190941.GB4187@phoenix>
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<5405C013 DOT 7030503 AT verizon DOT net> <87a96hrki4 DOT fsf AT Rainer DOT invalid> <54060378 DOT 2070108 AT gmail DOT com> <5406680D DOT 4030105 AT verizon DOT net> <540761FA DOT 1040902 AT verizon DOT net> <87ppfcqyc7 DOT fsf AT Rainer DOT invalid> <540A600A DOT 6090201 AT verizon DOT net> <540A6817 DOT 9080207 AT verizon DOT net> <20140906201229 DOT GA9220 AT phoenix> <20140908174606 DOT GA4187 AT phoenix>
MIME-Version:	1.0
In-Reply-To:	<20140908174606.GA4187@phoenix>
User-Agent:	Mutt/1.5.20 (2009-06-14)
X-IsSubscribed:	yes

On 2014-09-08, Gary Johnson wrote:
> On 2014-09-06, Gary Johnson wrote:
> > On 2014-09-05, Gerry Reno wrote:
> > 
> > > To clarify this request a bit:
> > > 
> > > Both run-1.2.0-1 and 1.3.1-1 are broken.  Neither one properly runs a command.
> > > The only recent package that actually worked was run-1.3.0-1.
> > 
> > That has not been my experience.  In my experience, run-1.2.0-1
> > works fine but 1.3.0-1 was broken, so I've been "keep"ing 1.2.0-1 on
> > my system until I hear that run has been fixed.
> > 
> > I'm sorry I don't have details on the problem with 1.3.0-1.  It
> > would just not work with the commands I was trying to execute.  I
> > believe there was some discussion about the issues on this list at
> > the time 1.3.0-1 was released.  I'm at home at the moment and away
> > from my Windows system so I can't experiment or look at the run
> > commands I use.
> 
> I wrote a batch file and a shell script to implement a Run Bash Here
> feature from the Windows file manager "Send to" context menu, much
> like chere but without having to mess with the registry.  The
> hardest part was getting the quoting in the run command line right
> so that both cmd and bash were happy.  The files are included
> in-line below.
> 
> When I updated to run-1.3, this stopped working.  That was a year
> ago and I don't remember the symptoms exactly:  the window either
> briefly appeared or there were no visible indications of the command
> running at all.  I fiddled with the quoting for a while and finally
> gave up and reverted to run-1.2.
> 
> I haven't tried the latest run-1.3.  I want to be sure I can still
> revert to run-1.2 if 1.3 doesn't work.  I may be able to try it this
> afternoon.

I tested the run command in my batch file by using my 64-bit Cygwin
installation to avoid breaking my 32-bit Cygwin installation.  (I
almost always use the 32-bit version because it originally had more
packages and I haven't seen any reason to switch.)  I first verified
that it worked with run-1.2, then upgraded to run-1.3.2-1.  It
failed.  Windows popped up, then disappeared.  I then added the
"-ha" option to mintty and ran the command again.  This time the
mintty window stayed and displayed this message:

    run_bash_here.sh: line 0: .: filename argument required
    .: usage: . filename [arguments]
    /bin/bash: Exit 2

I'm going to continue using run-1.2.0-1 on my 32-bit Cygwin
installation because it just works.

Regards,
Gary


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

- Raw text -