Message-ID: <4A8595CC.7090504@cwilson.fastmail.fm>
Date: Fri, 14 Aug 2009 12:50:20 -0400
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: run-1.1.11-1
References: <200908101812.n7AICVXY019082@gridley.byu.edu> <4A8239BC.8080401@byu.net> <20090812134355.GB13438@calimero.vinschen.de> <4A82F82C.6000907@cwilson.fastmail.fm> <20090813140610.GI13438@calimero.vinschen.de> <4A84BF50.3040009@cwilson.fastmail.fm> <20090814063458.GV13438@calimero.vinschen.de> <4A857186.9040201@cwilson.fastmail.fm> <20090814144442.GF32408@calimero.vinschen.de>
In-Reply-To: <20090814144442.GF32408@calimero.vinschen.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Corinna Vinschen wrote:

> I just tested this further.  If you omit the CREATE_NO_WINDOW flag
> to CreateProcess, the console window still flickers when starting
> urxvt, but the CPU usage does not stick to 100%.  Since XWin and
> xterm are apparently unaffected by this (no flickering cmd window)
> it looks like that's the better interim solution.
> 
> Sorry about that.  The CREATE_NO_WINDOW flag looked like a good idea 
> at the time(*)

Yeah.  I think the core issue is that run takes care to hook up stdin &
friends to the child process, but that something is going wrong in that
process when CREATE_NO_WINDOW -- and, for whatever reason, urxvt[d]-X
needs that (maybe also Ken Brown's bat -> bash -> emacs).

Anyway, I don't really want to delve into urxvt-7.7 right now and its
interaction with run+CREATE_NO_WINDOW. After cygwin-1.7 is released,
I'll start looking at (a) removing the unicode "shims" from
cygwin-urxvt, (b) switching to urxvt-9.x (c) compiling it to use
cygwin-1.7's unicode support.  That is, I don't want to invest too much
time in a dead-end version of urxvt (7.7).

As far as run itself is concerned, I'm (currently) happy to relegate any
problems to a W7 ghetto, until more people (including me) have access to
it and can worry those issues.

So, given a a /good-enough/ workaround for run+urxvt-7.7+W7, I don't
think you (Corinna) need to waste any more time on it now.

Tnanks,
Chuck

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