From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21983 invoked by alias); 23 Apr 2012 16:46:05 -0000 Received: (qmail 21948 invoked by uid 22791); 23 Apr 2012 16:46:03 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mdc1.cs.umass.edu (HELO csmail.cs.umass.edu) (128.119.240.121) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 23 Apr 2012 16:45:51 +0000 Received: from [10.1.40.241] (thingy.cs.umass.edu [128.119.40.196]) by csmail.cs.umass.edu (Postfix) with ESMTPSA id D4A6E200001DDD0BBC; Mon, 23 Apr 2012 12:45:49 -0400 (EDT) Message-ID: <4F95873A.4030006@cs.umass.edu> Date: Mon, 23 Apr 2012 16:46:00 -0000 From: Eliot Moss Reply-To: moss@cs.umass.edu User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: cygwin-xfree@cygwin.com Subject: Re: Issue with XWin under xlaunch References: <4F855BAC.7010809@cs.umass.edu> <4F955E58.8060403@dronecode.org.uk> <4F95864B.1090802@cs.umass.edu> In-Reply-To: <4F95864B.1090802@cs.umass.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com X-SW-Source: 2012-04/txt/msg00083.txt.bz2 On 4/23/2012 12:41 PM, Eliot Moss wrote: > Ok -- by perusing the log I figured it out ... > > In the past, .XWinrc names of files such as "xterm" > worked just fine. Apparently something changed about > the PATH used, and "xterm" was not being found. When > I write /usr/bin/xterm, it starts up. You can see the > first case and the second in the attached log file. > > So, I think xlaunch is ok, but this was a surprising > difference :-) ... > > Regards -- Eliot Moss PS -- I can confirm that adding /usr/bin solves the problem with the current released XWin.exe as well as with the 20120423 snapshot you asked me to test. E -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/