From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: XWin won't run xterm on start
Date: Wed, 24 Feb 2016 00:12:00 -0000 [thread overview]
Message-ID: <56CCF573.1050505@cornell.edu> (raw)
In-Reply-To: <56CCC418.3070307@ro.ru>
On 2/23/2016 3:42 PM, Jaakov wrote:
> Ken, I'll try your file, thanks a lot!
>
> But let us recapitulate that such files get outdated very quickly.
Your best defense against this is to read the xinit release
announcements. You can always ask for help if you want to change the
new behavior and aren't sure how.
Here are the last two announcements in which there were major changes to
the xinit package; both of them spelled out the changes very clearly:
https://sourceware.org/ml/cygwin-announce/2015-07/msg00013.html
https://cygwin.com/ml/cygwin-xfree-announce/2014-11/msg00004.html
Ken
--
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-24 0:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1456258759.50776.ezmlm@cygwin.com>
2016-02-23 20:42 ` Jaakov
2016-02-24 0:12 ` Ken Brown [this message]
2016-03-24 22:49 ` Mark Hansen
2016-03-24 22:52 ` Mark Hansen
2016-02-24 1:19 ` Jaakov
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
-- 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=56CCF573.1050505@cornell.edu \
--to=kbrown@cornell.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).