public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Ben Richards <benjamin.richards86@gmail.com> To: "cygwin-xfree@cygwin.com" <cygwin-xfree@cygwin.com> Subject: Need help to replicate old behavior of my X setup scripts with latest Xfree86 update Date: Tue, 23 Dec 2014 18:24:00 -0000 [thread overview] Message-ID: <CAFZuHrUBqDkvzkYeQfANh1QtHp0AXQ00zBhiR=S2W3B+9COfbQ@mail.gmail.com> (raw) 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. Before, when I ran startxwin it would launch the server and quit with an error status as to whether it was successful or not, leaving Xwin.exe running in the background. Now it stays in the foreground unless I specify otherwise. However, my startup script relied on the assumption that Xwin.exe was running by the time startxwinrc finished, which I cannot guarantee if I run it as a background task. It also used the exit status where if it was nonzero, I could assume that I already had X running and it wouldn’t kill the server if I typed ‘exit’ to exit any subsequent mintty windows I launched with Alt+F2. I've tried various configurations and read through the man pages but haven’t come up with an elegant solution other than the idea of looping on the ‘ps’ until I see Xwin.exe in the list. Is there a better way? Sincerely, Benjamin Richards -- 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 reply other threads:[~2014-12-23 18:24 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-23 18:24 Ben Richards [this message] 2014-12-23 19:17 ` Marco Atzeri 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='CAFZuHrUBqDkvzkYeQfANh1QtHp0AXQ00zBhiR=S2W3B+9COfbQ@mail.gmail.com' \ --to=benjamin.richards86@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: linkBe 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).