Re: 2.1.1 and xterm
Re: 2.1.1 and xterm
- Subject: Re: 2.1.1 and xterm
- From: William Mortensen <email@hidden>
- Date: Sat, 15 Dec 2007 18:27:13 -0800
On Dec 15, 2007, at 5:59 PM, John Koren wrote:
Merl
I understand that when DISPLAY is set to /tmp/launch-xxxx/:0 then
X11 windows are channeled through this socket. But what is the
benefit of doing it that way? What was wrong with the 'localhost'?
Why can't launchd set the DISPLAY to ':0'?
As I mentioned earlier going through localhost still seems to work.
If you go to terminal.app or xterm and set DISPLAY to ':0' or
'localhost:0' or 'your_computer_name:0' and try to launch an X
application it will open correctly on your local screen.
Only if the X server is already running. If you let DISPLAY stay as /
tmp/launch-blah/:0, then that works whether X11 is running or not.
What sort of problems does the new scheme cause for you? I am a little
worried by your email from earlier:
I like to bundle my applications but when I set the display to say :
0 (eg. rxvt -display :0) then the launcher does not start X11 or it
pops up an extra xterm, depending if it is a script or a bundle. Of
course I can rewrite all my scripts and bundles so that they do not
contain display :0 however it would be nice if the launcher was
smarter about it so I would not have to remember all these special
Mac-only details.
You shouldn't be setting DISPLAY at all, nor should your scripts/
bundles be explicitly launching X11. So I don't think I see how there
are any "special Mac-only details" to remember.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden