From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: XWin won't run xterm on start
Date: Mon, 22 Feb 2016 02:43:00 -0000 [thread overview]
Message-ID: <56CA75E5.7020607@cs.umass.edu> (raw)
In-Reply-To: <56CA6B68.4050400@cornell.edu>
On 2/21/2016 8:59 PM, Ken Brown wrote:
> On 2/21/2016 6:21 PM, Eliot Moss wrote:
>> On 2/21/2016 4:28 PM, Jaakov Jaakov wrote:
>>>
>>>> Why not do:
>>>
>>>> xterm ... &
>>>
>>>> /etc/X11/xinit/startxwinrc
>>
>> Do this in your personal .startxwinrc file ...
>
> Won't this lead to an infinite recursion? (See https://www.cygwin.com/ml/cygwin/2016-02/msg00325.html)
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 ...
EM
--
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
next prev parent reply other threads:[~2016-02-22 2:43 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 [this message]
2016-02-22 20:47 ` Jaakov
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=56CA75E5.7020607@cs.umass.edu \
--to=moss@cs.umass.edu \
--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).