From: "Jaakov Jaakov" <j_k_v@ro.ru>
To: "Marco Atzeri" <marco.atzeri@gmail.com>
Cc: "Cygwin" <cygwin@cygwin.com>
Subject: RE: Re: XWin won't run xterm on start
Date: Sun, 21 Feb 2016 19:16:00 -0000 [thread overview]
Message-ID: <1456082182.621336.15939.11409@mail.rambler.ru> (raw)
In-Reply-To: <56CA04E8.6020304@gmail.com>
> > 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
next prev parent reply other threads:[~2016-02-21 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 18:24 Jaakov Jaakov
2016-02-21 18:41 ` Marco Atzeri
2016-02-21 19:16 ` Jaakov Jaakov [this message]
2016-02-21 21:07 ` Eliot Moss
2016-02-21 21:28 Jaakov Jaakov
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=1456082182.621336.15939.11409@mail.rambler.ru \
--to=j_k_v@ro.ru \
--cc=cygwin@cygwin.com \
--cc=marco.atzeri@gmail.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).