public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jaakov <j_k_v@ro.ru>
To: cygwin@cygwin.com
Subject: Re: XWin won't run xterm on start
Date: Mon, 22 Feb 2016 20:47:00 -0000	[thread overview]
Message-ID: <56CB73C2.6010008@ro.ru> (raw)
In-Reply-To: <56CA468C.2010809@cs.umass.edu>

> 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

  parent reply	other threads:[~2016-02-22 20:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-21 21:28 Jaakov Jaakov
2016-02-21 23:21 ` Eliot Moss
2016-02-22  1:59   ` Ken Brown
2016-02-22  2:43     ` Eliot Moss
2016-02-22 20:47   ` Jaakov [this message]
2016-02-22 21:51     ` Ken Brown
2016-02-22 22:19       ` Ken Brown
2016-02-22 20:55   ` Jaakov
2016-02-22 21:52     ` Ken Brown
     [not found] <1456258759.50776.ezmlm@cygwin.com>
2016-02-23 20:42 ` Jaakov
2016-02-24  0:12   ` Ken Brown
2016-03-24 22:49   ` Mark Hansen
2016-03-24 22:52     ` Mark Hansen
2016-02-24  1:19 ` Jaakov
  -- strict thread matches above, loose matches on Subject: below --
2016-02-21 18:24 Jaakov Jaakov
2016-02-21 18:41 ` Marco Atzeri
2016-02-21 19:16   ` Jaakov Jaakov
2016-02-21 21:07     ` Eliot Moss
2016-02-21 14:38 Jaakov Jaakov
2016-02-21 17:27 ` Marco Atzeri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56CB73C2.6010008@ro.ru \
    --to=j_k_v@ro.ru \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).