This is the mail archive of the
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] Updated: run-1.1.11-1
On 8/17/2009 4:47 AM, Corinna Vinschen wrote:
On Aug 16 12:55, Charles Wilson wrote:
Colin Harrison wrote:
I am getting a stderr/pipe problem with some CUI's ~line 398 in run.c#$!%#
(1.1.11 run + your patch)
bForceUsingPipes = (os_version >= 0x0501);
I'd appreciate it.
I made this = FALSE to fix for 2003 server..not tried on Windows 7.
I'm still testing (run built with MinGW) so this is maybe a clue or just a
One failing CUI was plink (an ssh client from PuTTY).
I'll try and get back with more detail or a better fix!
I'm starting to suspect that there is no good mechanism to automatically
DTRT here for [cygwin-1.5/cygwin-1.7/mingw] x
[w95/98/Me/NT/2k/XP/Vista/Svr200x/W7] x [every app known to mankind],
and that a command line option to override the internal heuristics may
be required. Don't you just love Windows?
FWIW, I've added run to the cygwin-apps repository, here:
cvs -z3 -d:pserver:firstname.lastname@example.org:/cvs/cygwin-apps co run
but you'll need to 'autoreconf -fvi' before building it.
I had the idea to redirect to NUL: for the inferior process, so I
applied the below patch. Don't ask for a reason, it was just a hunch
that this might work.
Redirecting to /dev/null works fine for me on W7. With this patch, XWin
starts as expected when called from the `run startxwin.bat' shortcut,
xterm, gvim, xeyes all start fine, and, that's most interesting, urxvt
starts fine as well, without constantly taking 100% CPU. And yes,
*this* time I made sure that the shortcut actually calls urxvt-X via
run. In no case I have a flickering console window.
I'm not sure this a generic enough solution, there's probable more
necessary. However, would others be so kind to test this on non-W7
systems as well as with other applications like emacs?
Works for me on XP SP3. I tested the 'run startxwin.bat' shorcut, the
'run startemacs.bat' shortcut that I described earlier in the thread,
and a shortcut that contains 'C:\cygwin-1.7\bin\run.exe -p /usr/bin bash
-l -c "emacs --display=127.0.0.1:0.0"'. With both methods of starting
emacs, it starts as expected and runs without performance problems.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple