From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 41263 invoked by alias); 22 Feb 2016 20:47:05 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 41246 invoked by uid 89); 22 Feb 2016 20:47:05 -0000 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 Received: from huan2.mail.rambler.ru (HELO huan2.mail.rambler.ru) (81.19.66.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Mon, 22 Feb 2016 20:47:03 +0000 Received: from [UNAVAILABLE] ([91.52.0.124]:34459 helo=[192.168.3.203]) by huan2.mail.rambler.ru with esmtpa (Exim 4.76) (envelope-from ) id 1aXxNj-0004QY-KF for cygwin@cygwin.com; Mon, 22 Feb 2016 23:46:59 +0300 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 Message-ID: <56CB73C2.6010008@ro.ru> Date: Mon, 22 Feb 2016 20:47:00 -0000 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 X-SW-Source: 2016-02/txt/msg00354.txt.bz2 > 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