X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,TW_RX,TW_TK,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <4CA1EFC6.6030202@dronecode.org.uk> References: <4CA1C204.6090405@epfl.ch> <4CA1C3EE.1030204@ece.cmu.edu> <4CA1EFC6.6030202@dronecode.org.uk> Date: Wed, 29 Sep 2010 06:51:27 +0100 Message-ID: Subject: Re: mintty window won't open From: Andy Koppe To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On 28 September 2010 14:38, Jon TURNEY wrote: > On 28/09/2010 13:18, Andy Koppe wrote: >> On 28 September 2010 11:31, Ryan Johnson wrote: >>>> I switched from rxvt to mintty yesterday, and it worked great all day. >>>> However, today when I try to open a new mintty window from within an >>>> existing one, nothing happens. The process starts, but no window >>>> appears. This happens when attempting to open both 0.8.3 and 0.9b2 >>>> windows from a 0.9b2 window. The broken window also does the same thing >>>> to tkdiff but is able to run xterm without problems. >>>> >>>> Oddly, using the shortcut from the start menu (0.8.3) still works, and >>>> any windows I fire up from it (including 0.9b2) work fine after that and >>>> can in turn fire up their own new instances. >>> >>> I found the problem: the terminal was running an ssh session to >>> localhost. >> >> Ah yes, that would do it. > > I think you can detect this situation (no access to the interactive desktop > or whatever is it called), if you wished to issue a suitable error message, > by checking that OpenInputDesktop() returns non-NULL... Good idea, and that does seem to do the job. Opening a window in that situation seems to work fine anyway though. I guess it goes to some hidden desktop. Can anyone think of a sensible use case for that, i.e. should I make this a warning rather than an error? Andy -- 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