X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Tue, 18 Aug 2009 10:28:12 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: [ANNOUNCEMENT] Updated: run-1.1.11-1
Message-ID:	<20090818082812.GC32408@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<200908171705 DOT n7HH5TYe024203 AT StraightRunning DOT com> <4A89A490 DOT 1050108 AT cwilson DOT fastmail DOT fm> <4A89DC1F DOT 2050509 AT cwilson DOT fastmail DOT fm>
MIME-Version:	1.0
In-Reply-To:	<4A89DC1F.2050509@cwilson.fastmail.fm>
User-Agent:	Mutt/1.5.19 (2009-02-20)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Aug 17 18:39, Charles Wilson wrote:
> Charles Wilson wrote:
> 
> > If we already HAVE true console handles, then we shouldn't FreeConsole
> > and try to recreate our own...
> 
> OK, how about this?  Seems to work on Vista(cyg1.5, cyg1.7, mingw) x
> gui/cui/bat.
> 
> The basic idea is to try and re-use whatever console is available, if
> any, when run is started.  If this is the invisible console created by
> cygwin as part of process startup, great. If it is inherited from the
> calling window, fine.  But never try to explicitly hide the console if
> it already exists (that way, you can call 'run foo' from a cmd box
> without it disappearing on you).
> 
> Also, if creating a new console, then do it in the parent (run) process
> and hide it there -- even for W7, by using the message-only trick --
> instead of attaching to the child's console and manipulating it after
> the fact.
> 
> I *think* this slight refactoring will allow us to add any additional
> tweaks needed by W7 with only small, localized changes, so I'm hopeful
> that this patch can actual be checked in even if it is not perfect.

Big big big sigh.

And a big sorry for the hassle.

My only excuse is that I'm currently distracted by another project at my
company.

It turns out that all three attempts, starting with my NUL: patch, over
your previous one, up to this one work fine in all cases under W7.

XWin works, xterm works, gvim works, urxvt works (and doesn't take 100%
CPU).  Starting emacs with `run emacs-X11' works.

I made a dumb mistake when testing the `run bash -c emacs' variation.
It didn't work before with my and your former attempt because I failed
to add correct quotation.

This fails:

  run bash -c -l emacs --display=127.0.0.1:0.0

This works with all three variations:

  run bash -c -l "emacs --display=127.0.0.1:0.0"

See the small difference?

`run startemacs.bat' also works fine.  It didn't work for me because I
took the file content as is, without realizing that the Cygwin root dir
was set to C:\cygwin-1.7 in the script, while it's C:\cygwin on my
machine.  Urgh.

Again, sorry for the confusion. :(


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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

- Raw text -