public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-xfree@cygwin.com
Subject: Re: Need help to replicate old behavior of my X setup scripts with latest Xfree86 update
Date: Tue, 23 Dec 2014 19:17:00 -0000 [thread overview]
Message-ID: <5499BFC1.2030006@gmail.com> (raw)
In-Reply-To: <CAFZuHrUBqDkvzkYeQfANh1QtHp0AXQ00zBhiR=S2W3B+9COfbQ@mail.gmail.com>
On 12/23/2014 7:24 PM, Ben Richards wrote:
> Up until the recent update to xinit-1.3.4-1 which overhauled X session
> handling, I had my session set up nicely for my purposes. With the
> following code in my .zshrc and an empty .startxwinrc, when I launched
> Cygwin, Xwin.exe would start on display :0.0, it would set the
> $DISPLAY variable, and automatically kill the X server when I exited
> that terminal. I like mintty so this let me use that as my shell.
>
> .zshrc contents:
> =============
> startxwin &> xserver.log
> x_start_success=$?
> if [[ $x_start_success == 0 ]]; then
> export DISPLAY=:0.0
>
> pid=`ps | grep '/usr/bin/XWin' | awk '{print $1;}'`
> alias kill_xwin="kill $pid"
> if [[ $TMUX == "" ]] && [[ $x_start_success == 0 ]]; then
> alias exit="kill $pid ; \exit"
> fi
> fi
>
> The aforementioned update disrupted this flow so Iâm wondering if
> anyone has any suggestions on how I can regain a similar sort of
> functionality. I donât like using xterm in Cygwin and would like to
> keep using mintty as my main terminal interface.
try putting "sleep inf" in .startxwinrc
It should simulate the old behaviour
Regards
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
next prev parent reply other threads:[~2014-12-23 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 18:24 Ben Richards
2014-12-23 19:17 ` Marco Atzeri [this message]
2014-12-24 17:47 ` Jacob Niehus
2015-01-09 18:55 ` Benjamin Richards
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=5499BFC1.2030006@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-xfree@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).