This is the mail archive of the
mailing list for the Cygwin project.
Re: latest cygwin: 'run' problem
- From: Gary Johnson <garyjohn at spocom dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 8 Sep 2014 12:09:41 -0700
- Subject: Re: latest cygwin: 'run' problem
- Authentication-results: sourceware.org; auth=none
- 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>
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
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.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple