X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-3.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4A859A59.1040308@cwilson.fastmail.fm> Date: Fri, 14 Aug 2009 13:09:45 -0400 From: Charles Wilson 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: <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> <20090814151921.GA28983@ednor.casa.cgf.cx> <20090814152904.GG32408@calimero.vinschen.de> <20090814154349.GA10002@ednor.casa.cgf.cx> <20090814162049.GH32408@calimero.vinschen.de> In-Reply-To: <20090814162049.GH32408@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 List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 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 and #2. 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... Heh. -- 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