X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=WOGsSdXIhBbJRuyH
	aIF3aJntWWgou9COMcUlR3bjnZ5R2utaE/Ub+NNR19BlJGgcUMeyQWlNTb9GHEuQ
	rpTUpIG+q2BzskVolRBC/MyfG9wcbpUvxTkdPIEMkYpaTO1cr3qNyorUIYSQUysJ
	xVWx2/zNtOnpGDkfq6srOPPKlYI=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=Y9VORk5oCw4zSnls8NtrB+
	5XWVo=; b=yBFzNxPqPefwZxO7axCAoklFckFcM1U1JYmwlMAO5OkDowynJQ/Yhv
	l8K566rhdZxwDDaQWQW2E2T/lnxPXp70ltrw1k7j50x2muZArlzAG2qBZ979CJaj
	WXLrFrCDCRwAS66BmKDbQ/lemlQVk7MbztrDXuIS6xvc19o+0hf7o=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: Yes, score=5.5 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE,RCVD_IN_RP_RNBL,SPF_PASS autolearn=no version=3.3.2 spammy=freshly, H*r:4.76, H*RU:!UNAVAILABLE!, H*r:UNAVAILABLE
X-HELO: huan2.mail.rambler.ru
Subject: Re: XWin won't run xterm on start
To: cygwin@cygwin.com
References: <1456090085.415814.30486.4659@mail.rambler.ru> <56CA468C.2010809@cs.umass.edu>
From: Jaakov <j_k_v@ro.ru>
Message-ID: <56CB73C2.6010008@ro.ru>
Date: Mon, 22 Feb 2016 21:46:58 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.5.0
MIME-Version: 1.0
In-Reply-To: <56CA468C.2010809@cs.umass.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Rambler-User: j_k_v@ro.ru/91.52.0.124

> Ah, perhaps.  There may be ways to catch that, but it may be easier for the
> OP to copy the startxwinrc file's contents.  Not the best for responding to
> future changes ...

One way to prevent recursion is

if [[ "$FILEINCLUDED" != "1" ]];
then
   export FILEINCLUDED=1
   ...  # do real job here
fi

However, placing this either into the systemwide startxwinrc or into the 
local .startxwinrc would not do anything useful.

The right thing to do would be to append a call to 
$HOME/.startxwinrc_final (this name is freshly invented, feel free to 
change) at the end of the systemwide startxwinrc. An alternative would 
be to call $HOME/.startxwinrc_final from the same place from where the 
systemwide startxwinrc is called; namely right after it.

Anyone feeling of doing this?

Thanks!

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

