delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,TW_RX,TW_TK |
X-Spam-Check-By: | sourceware.org |
Message-ID: | <4CA1EFC6.6030202@dronecode.org.uk> |
Date: | Tue, 28 Sep 2010 14:38:14 +0100 |
From: | Jon TURNEY <jon DOT turney AT dronecode DOT org DOT uk> |
User-Agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 |
MIME-Version: | 1.0 |
To: | cygwin AT cygwin DOT com |
Subject: | Re: mintty window won't open |
References: | <4CA1C204 DOT 6090405 AT epfl DOT ch> <4CA1C3EE DOT 1030204 AT ece DOT cmu DOT edu> <AANLkTinm7jU3yC7FM+bQyp6FzwYoYb+M8L524bzFXGu=@mail.gmail.com> |
In-Reply-To: | <AANLkTinm7jU3yC7FM+bQyp6FzwYoYb+M8L524bzFXGu=@mail.gmail.com> |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.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 28/09/2010 13:18, Andy Koppe wrote: > On 28 September 2010 11:31, Ryan Johnson wrote: >> On 9/28/2010 12:23 PM, 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... -- 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |