Re: randomly dying xterms: not random
Re: randomly dying xterms: not random
- Subject: Re: randomly dying xterms: not random
- From: Ronald Cohen <email@hidden>
- Date: Sun, 26 Oct 2008 11:13:44 -0700
Thanks to all for the responses. I now recall what is the problem
with my workaround, which is to not start up an xterm from
org.x.X11.plist, but rather by having it in a .xinitrc, which is that
the display variable gets explicitly set in the latter case, rather
than via launchd, and this creates problems when moving my laptop to
another network.
So it would be good to get a solution to the disappearing xterm
problem as posted. I guess the alternative is to get in the habit of
launching x11 by starting an xterm from terminal.app.
-Ron-
On Oct 24, 2008, at 4:02 PM, Jeremy Huddleston wrote:
On Oct 24, 2008, at 15:41, Ronald Cohen wrote:
Update: The behavior is completely reproducible. It happens
whenever I do the following:
Start up X11. I am running without my own .xinitrc so it is
starting up vanilla. Start up some process in the xterm that
appears. Open a new xterm from the X11 Applications menu (the
Terminal command is set to open an xterm). The first xterm
freezes and its process dies.
I do not see that... and I'm sure if this were the case, it'd've
been reported already... there's probably something odd with your
environment or something...
If I repeat the above but don't start up a process in the initial
xterm, then when I open up the second xterm, the first one
disappears.
Again... odd... ?
If I instead open up additional xterms by typing "xterm" in the
initial xterm or any subequently created xterm, the above does not
happen. The initial xterm survives and remains alive. (So for
example if I create a second xterm before starting a process in the
first xterm, then open a third xterm from the second, all three
xterms and the process in the first xterm remain alive. If however
I then attempt to start an xterm from the application window, the
initial xterm dies.)
I guess I have a workaround -- bugger org.x.x11.plist so that the
initially launched process is effectively nothing (for example
xlsclients, as suggested in macosxhints)
You don't need that. Just run true instead... it doesn't need to be
an x client.
and then execute a .cshrc that launches my initial xterm. Haven't
tried this yet....
uhm... you should not be putting anything like xterm in your .cshrc
I wonder if this problem is unique to the fact that you are using
csh instead of bash... do you have this problem if you use the
default shell?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden