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:from:to:cc:reply-to:subject:date
	:content-transfer-encoding:content-type:in-reply-to:message-id
	:mime-version:references; q=dns; s=default; b=Z6IjQWSWuT5a9i8z+l
	WBMoH0IKhvOhn0lW1Xos6YG03qmw4UxyFZwdGr9ZTrsLMhMod+8XymtCpWTQv3y6
	gYHBcELkvaZdE13uxQcohDKa95BluDTXlLwbT8NJbmrhWlj4xk40ceAXE8El1sEj
	jo15yTJdGuHZYZJ8pIon835SI=
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:from:to:cc:reply-to:subject:date
	:content-transfer-encoding:content-type:in-reply-to:message-id
	:mime-version:references; s=default; bh=bnGYYXpP3Tj2Y/2SreAg6w7B
	y6A=; b=oPYFfPY/kY3866ogCAHY96AFieUrR5GtoEmv3sDTJyrBaLQ8TAb/z6fG
	5UkpzXyy+Thbibko9fO+eV6NZXVRXPbLCNl+2O70v58K/Uxs4nRLtMJuZ7ihTd8a
	ndJAm0hh58BoxkiV3kddtz/zN6LIvUp0qGCPwgiEV8NUqg3vSUE=
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=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=HCc:D*cygwin.com, H*MI:sk:56CA04E, HCc:U*cygwin, H*f:sk:56CA04E
X-HELO: mxout2.rambler.ru
From: "Jaakov Jaakov" <j_k_v AT ro DOT ru>
To: "Marco Atzeri" <marco DOT atzeri AT gmail DOT com>
Cc: "Cygwin" <cygwin AT cygwin DOT com>
Reply-To: "Jaakov Jaakov" <j_k_v AT ro DOT ru>
Subject: RE: Re: XWin won't run xterm on start
Date: Sun, 21 Feb 2016 22:16:22 +0300
Content-Disposition: inline
Content-Type: text/plain; charset="utf-8"; format="flowed"
In-Reply-To: <56CA04E8.6020304@gmail.com>
Message-Id: <1456082182.621336.15939.11409@mail.rambler.ru>
MIME-Version: 1.0
References: <56CA04E8 DOT 6020304 AT gmail DOT com>
X-Rambler-User: j_k_v AT ro DOT ru/87.174.129.54
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u1LJGbIs014697


> > Dear Marco:
> >
> > So, are you saying that not starting xterm is by design?
> 
> yes
> 

Well, then, apparently, the design changed several months ago.

> >> http://x.cygwin.com/docs/man1/startxwin.1.html
> >
> > The manpage above is a bit outdated; creating a .startxwinrc with
> >
> > xrdb -load $HOME/.Xresources
> > xbiff -geometry -430+5 &
> > oclock -geometry 75x75-0-0 &
> > xload -geometry -80-0 &
> > xterm -geometry +0+60 -ls &
> > xterm -geometry +0-100 &
> > xconsole -geometry -0+0 -fn 5x7 &
> > exec fbpanel -profile multiwindow
> >
> > and running startxwin from the text console results in
> >
> > ---
> 
> It is an example....
> 
> try just
> 
> xterm -geometry +0+60 -ls &
> xterm -geometry +0-100 &
> exec    xclock
> 
> killing xclock will shutdown the X server.
> You can use any other program for that.
> 
> 
Thank you, I see. I cannot use xclock - we have one clock in Windows(TM) already, but I'll choose something.
Is there any way to do whatever the current version of
/etc/X11/xinit/startxwinrc 
does (xwin-xdg-menu, gnome-keyring-daemon, and lots of other goodies which I sometimes need) and, in addition (as opposed to "instead"), run uxterm?

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