Re: X11 article, for review (take 2)
Re: X11 article, for review (take 2)
- Subject: Re: X11 article, for review (take 2)
- From: Rich Morin <email@hidden>
- Date: Thu, 3 Apr 2003 22:05:44 -0800
At 8:23 PM -0600 4/3/03, Randy Ford wrote:
Sorry this reply is days late: I just found that I didn't send it.
These things happen. In the meanwhile, however, I sent an edited draft
to my editors; let's hope It's close enough (:-). Most of the text is
the same, FWIW, but I moved some sections around and tried to make the
caveats clearer. A copy is online at
http://www.cfcl.com/rdm/section7/2003.05.X11.6.pdf
This sounds unrelated to the above. Ssh (the client) has to connect
and authenticate with the X server. Stopping the X server broke that
connection. It's not related to how DISPLAY got set. You didn't
need to exit Terminal, just to exit the ssh session and restart it.
Actually, all I have to do is restart the window manager.
It's as easy as copying some lines into ones ~/.Xresources or
~/.Xdefaults. ...
I don't see a copy of those lines in my email; feel free to send them.
If someone just wants to run occasional X11
apps, they shouldn't have to buy into xterm in the process.
Agreed. I believe that is why Apple designed the "Applications" item
on the X11 menu. Given the massive amount of X11 software and the
variety of it, one who is using the shell often will probably also be
using X11 often. Similarly, one using ssh often, especially if they
are sending X11 programs back to their display, will probably either
be comfortable in the shell, or will just set up an item in the
Applications menu.
I imagine so. My case is a bit peculiar; I need to get the standard
output from the program (for trace output) while I'm debugging it.
If you log into this account from another box, even using ssh -X,
your DISPLAY will be set to :0.
Let's call "another box" frodo. If DISPLAY is unset on frodo, and
I log in from there to cerberus, my .login file on cerberus will set
DISPLAY to ':0'.
When you try to launch an X11 program, it will not display on the
machine you are using (the "other" box); it will attempt to be
displayed on the machine that you are remotely connected to.
That is, the window will show up on cerberus, rather than frodo.
If it is successful, it appears on the shell session to fail without
any error message. If it fails, it gives an "Unable to connect"
message instead of a "DISPLAY not set" one.
That makes a peculiar sort of sense (:-). Now, what do I do about
it? How about making the .login code a bit smarter?
if (! $?DISPLAY) then
switch ("`who am i`")
case '.*)': breaksw
default: setenv DISPLAY ':0'; breaksw
endsw
endif
AFAIK, this handles the case you mention. Are there any other
known pitfalls I need to cover?
-r
--
email: email@hidden; phone: +1 650-873-7841
http://www.cfcl.com/rdm - my home page, resume, etc.
http://www.cfcl.com/Meta - The FreeBSD Browser, Meta Project, etc.
http://www.ptf.com/dossier - Prime Time Freeware's DOSSIER series
http://www.ptf.com/tdc - Prime Time Freeware's Darwin Collection
_______________________________________________
x11-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/x11-users
X11 for Mac OS X FAQ: http://developer.apple.com/qa/qa2001/qa1232.html
Report issues, request features, feedback: http://developer.apple.com/bugreporter
Do not post admin requests to the list. They will be ignored.