public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: xinit-1.3.4-1 (Major overhaul of X session handling)
Date: Fri, 05 Dec 2014 13:35:00 -0000 [thread overview]
Message-ID: <5481B4A6.8010009@dronecode.org.uk> (raw)
In-Reply-To: <CA+2x6-+chAGSokz9JRpz_FSoKq+OCQNzzyFq1gbkEqAJM-EWVA@mail.gmail.com>
On 29/11/2014 20:19, Nem W Schlecht wrote:
> On Fri, Nov 28, 2014 at 8:46 PM, Marco Atzeri wrote:
>> On 11/29/2014 3:05 AM, Nem W Schlecht wrote:
>>> * User-defined ~/.startxwinrc files must now be executable, the
>>> final command therein must be run in the foreground, and that
>>> command's exiting will end the X session, just like with startx
>>> and ~/.xinitrc or ~/.Xclients.
>>>
>>> In most UNIX systems, this last command would be the window manager.
>>> I'm not liking fbpanel (although I will give it a try) and I don't
>>> like using an XTerm as my "last" command, since I often close/reopen
>>> them all when making changes to my .bashrc/.bash_profile.
>>>
>>> Are there any suggestions from the list for some *other* program that
>>> won't use any resources that I can use as my final foreground command?
>>> I don't want it to do anything, just not let X11 exit.
>
> I just want X11 to *not*
> launch fbpanel and to *not* quit. For now, I've settled on just
> calling 'sleep' for 10 years.
If you previously had an empty ~/.startxwinrc, I'd suggest putting
'sleep infinity' or even 'exec sleep infinity' into it.
--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer
--
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-05 13:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 3:04 Yaakov Selkowitz
2014-11-28 8:45 ` Marco Atzeri
2014-11-28 11:54 ` Jon TURNEY
2014-11-28 22:53 ` Ken Brown
2014-11-30 4:02 ` Yaakov Selkowitz
2014-11-30 6:36 ` Nem W Schlecht
2014-11-30 7:45 ` Yaakov Selkowitz
2014-11-30 13:57 ` Ken Brown
2014-12-01 18:15 ` Jim Reisert AD1C
2014-12-01 18:16 ` Jim Reisert AD1C
2014-11-29 2:05 ` Nem W Schlecht
2014-11-29 2:46 ` Marco Atzeri
2014-11-29 20:19 ` Nem W Schlecht
2014-12-05 13:35 ` Jon TURNEY [this message]
2014-12-05 14:51 ` Nem W Schlecht
2014-11-30 0:18 Angelo Graziosi
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=5481B4A6.8010009@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).