From: Marco Atzeri <marco.atzeri@gmail.com>
To: Jaakov Jaakov <j_k_v@ro.ru>, Cygwin <cygwin@cygwin.com>
Subject: Re: XWin won't run xterm on start
Date: Sun, 21 Feb 2016 18:41:00 -0000 [thread overview]
Message-ID: <56CA04E8.6020304@gmail.com> (raw)
In-Reply-To: <1456079088.987566.21611.60107@mail.rambler.ru>
On 21/02/2016 19:24, Jaakov Jaakov wrote:
>
> Dear Marco:
>
> So, are you saying that not starting xterm is by design?
yes
>> 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.
--
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-21 18:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 18:24 Jaakov Jaakov
2016-02-21 18:41 ` Marco Atzeri [this message]
2016-02-21 19:16 ` Jaakov Jaakov
2016-02-21 21:07 ` Eliot Moss
[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 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
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
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=56CA04E8.6020304@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
--cc=j_k_v@ro.ru \
/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).