X-Recipient: archive-cygwin AT delorie DOT 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=cfBF0LazzqBry79J
	PxSveQXeMZeABAEONkUiV2pO5hvgVECoRKW9RO4GykLK+BNNUPn4nRvgycWaT8bu
	T2REdBukpEGLGFvwNfsfho16nZIeQ6ScGQ1I8mX2xQ3OUafGk/hgaDMogG6/ydS6
	70UtvGXUREszeWEzX8HrXIEu3n0=
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=VAhx0IckwWh1zKZJpIhAg+
	yyK5Q=; b=wOHuswUiR591S3iKdpLW6rIsf1jU1EbvvDbE3TsktgO538yUshWGAT
	lFXcvhJaJA6fiFucW+IIjWwPmDgahnJA0j8WIhNTE2/Dci9fHdSgYbdGGPSFZrO1
	tdF0LI24ub7qoL2PKM/+fMctr2vAIupxeYGOmHRuO+0aKro5SOLHc=
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.0 required=5.0 tests=BAYES_40,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 spammy=freshly, $FILEINCLUDED, FILEINCLUDED, fileincluded
X-HELO: limerock02.mail.cornell.edu
X-CornellRouted: This message has been Routed already.
Subject: Re: XWin won't run xterm on start
To: cygwin AT cygwin DOT com
References: <1456090085 DOT 415814 DOT 30486 DOT 4659 AT mail DOT rambler DOT ru> <56CA468C DOT 2010809 AT cs DOT umass DOT edu> <56CB73C2 DOT 6010008 AT ro DOT ru>
From: Ken Brown <kbrown AT cornell DOT edu>
Message-ID: <56CB82F2.3070506@cornell.edu>
Date: Mon, 22 Feb 2016 16:51:46 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <56CB73C2.6010008@ro.ru>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 2/22/2016 3:46 PM, Jaakov wrote:
>> 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?

There's no need for this complexity.  If you don't like what the system 
startxwinrc does, just copy it to ~/.startxwinrc and modify it to suit 
your purposes.

Ken


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