Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Envelope-To: cygwin AT cygwin DOT com X-Comment-To: Andy Piper To: Andy Piper Cc: xemacs-winnt AT xemacs DOT org, ben AT xemacs DOT org, cygwin AT cygwin DOT com Subject: Re: Xemacs/cygwin 21.4.3 and new console window during compilation References: <4 DOT 3 DOT 2 DOT 7 DOT 2 DOT 20011217182832 DOT 00b23e48 AT san-francisco DOT beasys DOT com> From: Dmitry Bely Date: 18 Dec 2001 11:11:10 +0300 In-Reply-To: <4.3.2.7.2.20011217182832.00b23e48@san-francisco.beasys.com> Message-ID: Lines: 23 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Civil Service (Windows)) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Andy Piper writes: > So my supposition is that a console window is created because XEmacs > doesn't have one by default when started from the desktop. Why then MSVC-compiled XEmacs does not popup new console in the same situation? It also seems not to have one by default ... > The reason > it works in bash is that children inherit their parent's console by > default and somewhere up the foodchain cygwin has a console. I have no > idea how we could fix this. I imagine that if we do AllocConsole in > the cygwin version of XEmacs that whilst this may stop your program > creating a console we will get an ugly console popping up for XEmacs > as a whole. Maybe this is acceptable, I don't know. I'm CC'ing ben and > the cygwin list to see if any windows gurus have any great ideas on > this score. > > > andy Hope to hear from you soon, Dmitry -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/