This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: Updated: run-1.3.0-1
- From: Tim Adye <T dot J dot Adye at rl dot ac dot uk>
- To: 'The Cygwin Mailing List' <cygwin at cygwin dot com>
- Date: Sat, 14 Sep 2013 00:58:16 +0100
- Subject: RE: Updated: run-1.3.0-1
- Authentication-results: sourceware.org; auth=none
- References: <20130724224102 dot DEB28C00E84 at frontend1 dot nyi dot mail dot srv dot osa>
Hi Charles,
Just to follow up on the problem that was discussed a couple of months ago
(Angelo Graziosi's initial report copied below), I have similar problems
with run-1.3.0-1 that were not present in run-1.2.0-1.
I made a simple example that perhaps shows the problem more clearly: with an
X-server running (and xmessage installed), from the Windows Command Prompt:
C:\cygwin\bin\run.exe xmessage "a b"
With run-1.2.0-1, this shows the message with several spaces between the "a"
and "b" as given on the command line, but in run-1.3.0-1, all but one of the
spaces are dropped. I guess the new version of run is not interpreting the "
quotes correctly and xmessage is receiving two arguments "a" "b" (debug
printout shows this), which it separates with a single space. The same
happens if I use /usr/bin/run from the bash shell.
One can get the correct spacing by adding an extra level of quoting, eg.
C:\cygwin\bin\run.exe xmessage "'a b'"
(single quotes inside double quotes, or vice versa).
Of course it's not so serious with this example, but bash -c (as Angelo and
I use) requires the full command to be passed as a single option argument.
Using the extra quoting is a work-around, but it's inconsistent and
confusing.
Sorry for the noise if this was already obvious, but I thought this might be
an extra hint.
I'm using 32-bit Cygwin 1.7.25-1, freshly installed on 64-bit Windows 8.
Regards,
Tim.
=========================== cut here ============================
Tim Adye T.J.Adye@rl.ac.uk http://hepunx.rl.ac.uk/~adye
ATLAS Group, Particle Physics Dept, Rutherford Appleton Lab
=========================== cut here ============================
Angelo Graziosi wrote on 25 Jul 2013:
>
> After this update, my Cygwin installation is basically broken. I have
> several links on desktop to start Cygwin applications and they don't
> work any more. The links target sound like these:
>
> C:\cygwin-2\bin\run.exe bash -l -c 'rm -rf /tmp/{.X*,dbus*,orbit*,*};
> XWin -nowgl -multiwindow -clipboard -silent-dup-error 2>/dev/null &'
>
> C:\cygwin-2\bin\run.exe bash -l -c 'GSETTINGS_BACKEND=memory emacs
> -display 127.0.0.1:0.0 2>/dev/null &'
>
> C:\cygwin-2\bin\run.exe bash -l -c 'urxvt-X -display 127.0.0.1:0.0 -ls
> -e /bin/bash -l 2>/dev/null &'
>
> etc...
>
> They worked fine for years without any problem. Reverting the update to
> previous version 1.2 of "run" allow the applications to work fine again.
-----Original Message-----
From: cygwin-announce-owner@cygwin.com On Behalf Of Charles Wilson
Sent: 24 July 2013 23:40
To: cygwin-announce@cygwin.com
Subject: Updated: run-1.3.0-1
The run package provides a simple application to launch console programs
with their console hidden.
This is a bugfix update. It should operate as normal on cygwin-1.7.21 as
well as other versions of cygwin. All previous versions of run, including
1.2.0-1, are broken on cygwin-1.7.21 and newer unless recompiled on
cygwin-1.7.22 to take advantage of a compile-time fix that version of cygwin
introduce.
Note that this package was NOT compiled on cygwin-1.7.22, and does NOT
employ cygwin's new compile-time fix; instead, run's own code was corrected
to work properly, with the cygwin-1.7.21+ runtime behavior.
CHANGES since run-1.2.0-1
============================
* Avoid failure on cygwin-1.7.21 vs. GetCommandLine not being populated.
This was fixed in cygwin-1.7.22 but it's good to clean up this code
anyway.
* Massive refactoring to share implementations (at the source code
level) with run2.
* -wait need not be the first argument
* New options --run-nogui, --run-notty, --run-verbose,
and --run-debug[=N] controlling how run.exe itself reports
error conditions and other messages.
+ By default, it is silent. If any messages are enabled
via --run-verbose or --run-debug=N, then they will either
be reported on stderr, or in windows popup boxes.
+ stderr is used if run.exe is launched from the cmdline, or
if --run-nogui.
+ Windows popup boxes are used if run.exe is launched by
doubleclicking it or by a Windows shortcut, or if --run-notty.
--
Charles Wilson
volunteer run maintainer for cygwin
====================================================================
To update your installation, click on the "Install Cygwin now" link on the
http://cygwin.com/ web page. This downloads setup.exe to your system.
Then, run setup and answer all of the questions.
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the cygwin-announce mailing list, look at
the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there. It will be in the format:
cygwin-announce-unsubscribe-you=yourdomain.com@cygwin.com
If you need more information on unsubscribing, start reading here:
http://sourceware.org/lists.html#unsubscribe-simple
Please read *all* of the information on unsubscribing that is available
starting at this URL.
--
Scanned by iCritical.
--
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