This is the mail archive of the
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] Updated: run-1.1.11-1
Corinna Vinschen wrote:
> Actually, what I told above is nonsense anyway. What I saw was the
> flickering cmd window from a urxvt-X startup without run. With run it
> doesn't start at all for me on W7, unless I start it from an existing
> console window. And in that case it doesn't matter if the
> CREATE_NO_WINDOW flag is given or not, it always takes 100% CPU. So,
> scratch that, it's no solution at all.
Rats. So much for a "good enough" workaround.
> I have no idea why urxvt-X doesn't start from my shortcut, which
> simply contains:
> C:\cygwin\bin\run.exe urxvt-X -display 127.0.0.1:0.0 -ls
Hmm. Run uses $PATH to search but it prepends "." and dir-of-run.exe, so
it really should find urxvt-X.exe. Three suggestions, in increasing
order of desperation:
#1: specify the explicit (cygwin) path to urxvt-X:
C:\cygwin-1.7\bin\run.exe /usr/bin/urxvt-X.exe -display 127.0.0.1:0.0 -ls
#2: also explicitly specify the shell
C:\cygwin-1.7\bin\run.exe /usr/bin/urxvt-X.exe -display 127.0.0.1:0.0
-ls -e /bin/bash --login
#3: recompile run.exe with -DDEBUG. This will cause a bunch of
MessageBoxes to appear with debugging information. And then repeat #1
FYI, one of my ideas for run.exe development is to improve its option
parsing and error message reporting, similar to run2's. (Also, support
--debug=LEVEL so you don't need to recompile for this sort of investigation)
> It sounds a lot as if I need a couple of hours refreshing...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple