http://apollo.homeunix.net/macports .... I am most glad to say, finally done! I am quite happy with how it turned out, but I am aware it could, both, see many improvements to what's there now (it feels a tad toooo wordy in some places, for instance) and, also, general improvements going forward (flow redesign, reworked sections, new ones, yanked ones, integration with James' mpwa, whatever...). But in any case that's what we have for now and what I'll be rolling live along our 1.6.0 release. Once again I tell you, review and feedback are most welcomed so don't be shy to speak up if you have anything to say, but at this point in the game I'm afraid I will not be able to make any structural changes for the time being (for one, my current share of spare time is running out). So, overall, enjoy our new project website! Thanks to all those who participated and provided feedback and help, specially to Chris for providing the basic structural design, artwork and CSS, much appreciated! Regards,... -jmpp
On Nov 22, 2007, at 1:08 PM, Juan Manuel Palacios wrote:
http://apollo.homeunix.net/macports .... I am most glad to say, finally done!
I am quite happy with how it turned out, but I am aware it could, both, see many improvements to what's there now (it feels a tad toooo wordy in some places, for instance) and, also, general improvements going forward (flow redesign, reworked sections, new ones, yanked ones, integration with James' mpwa, whatever...).
But in any case that's what we have for now and what I'll be rolling live along our 1.6.0 release. Once again I tell you, review and feedback are most welcomed so don't be shy to speak up if you have anything to say, but at this point in the game I'm afraid I will not be able to make any structural changes for the time being (for one, my current share of spare time is running out).
So, overall, enjoy our new project website! Thanks to all those who participated and provided feedback and help, specially to Chris for providing the basic structural design, artwork and CSS, much appreciated!
Regards,...
-jmpp
very nice indeed! on the installation page: "By far the simplest intallation procedure" should be ....installation... More important, further down the page has: Add an appropriate X11 DISPLAY environment variable to run X11 dependent programs. Im not sure you wish to do that with Leopard. In my own case, I have no ~/.xinitrc nor any DISPLAY=0.0 (or any other value), and this seems to give the best results..... (in other words letting the system set configuration for me.) The site looks great overall. :) William Davis frstanATbellsouthDOTnet Mac OS X.5.1 Darwin 9.1.0 Xquartz-1.2a11 Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non
On Nov 22, 2007, at 3:28 PM, William Davis wrote:
very nice indeed!
on the installation page:
"By far the simplest intallation procedure" should be ....installation...
Fixed!
More important, further down the page has:
Add an appropriate X11 DISPLAY environment variable to run X11 dependent programs.
Im not sure you wish to do that with Leopard. In my own case, I have no ~/.xinitrc nor any DISPLAY=0.0 (or any other value), and this seems to give the best results..... (in other words letting the system set configuration for me.)
I'll look into that shortly, I haven't played with X11 under Leopard yet so I wouldn't know what's best to advise. Thanks for bringing it up, though.
The site looks great overall. :)
Thank you for the feedback! ;-) Regards,... -jmpp
On Nov 22, 2007, at 2:28 PM, William Davis wrote:
On Nov 22, 2007, at 1:08 PM, Juan Manuel Palacios wrote:
http://apollo.homeunix.net/macports .... I am most glad to say, finally done!
It looks great. And XHTML valid! -- Frank Rietta MS InfoSec Student Georgia Institute of Technology Note: I check e-mail once or twice per business day.
On 2007-11-22 15:38:50 -0400, Juan Manuel Palacios wrote:
On Nov 22, 2007, at 3:28 PM, William Davis wrote:
More important, further down the page has:
Add an appropriate X11 DISPLAY environment variable to run X11 dependent programs.
Im not sure you wish to do that with Leopard. In my own case, I have no ~/.xinitrc nor any DISPLAY=0.0 (or any other value), and this seems to give the best results..... (in other words letting the system set configuration for me.)
I'll look into that shortly, I haven't played with X11 under Leopard yet so I wouldn't know what's best to advise. Thanks for bringing it up, though.
I don't have Leopard yet, but there have been discussions in the x11-users Apple list. On Leopard, DISPLAY is set to some special value so that the X11 server can be started automatically. So, setting it to :0 may break things. From one of the latest mail from Ben Byer: * Various X11 application .app bundles are now broken because they explicitly set $DISPLAY and/or try to launch X11 for you. and the explanation from an earlier one: ------------------------------------------------------------------------ The way that this is accomplished is by some slight-of-hand with the $DISPLAY variable -- if you look, it should be something like "/tmp/ launch-vbXRyu/:0". If an X client connects to this, it will actually connect to launchd, which will start Xquartz if needed and pass the client's socket to the server. All of that should be invisible to you; the X client library (libX11.dylib) was modified to support this, and all X11 applications link against this library. "DISPLAY=:0" would still work if X11.app is already running, but it will not trigger X11 to launch. ------------------------------------------------------------------------ BTW, I suppose that the X11 apps from MacPorts should also by linked to this modified library. -- Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
On Nov 22, 2007, at 7:30 PM, Vincent Lefevre wrote:
I don't have Leopard yet, but there have been discussions in the x11-users Apple list. On Leopard, DISPLAY is set to some special value so that the X11 server can be started automatically. So, setting it to :0 may break things. From one of the latest mail from Ben Byer:
* Various X11 application .app bundles are now broken because they explicitly set $DISPLAY and/or try to launch X11 for you.
and the explanation from an earlier one:
------------------------------------------------------------------------ The way that this is accomplished is by some slight-of-hand with the $DISPLAY variable -- if you look, it should be something like "/tmp/ launch-vbXRyu/:0". If an X client connects to this, it will actually connect to launchd, which will start Xquartz if needed and pass the client's socket to the server.
All of that should be invisible to you; the X client library (libX11.dylib) was modified to support this, and all X11 applications link against this library. "DISPLAY=:0" would still work if X11.app is already running, but it will not trigger X11 to launch. ------------------------------------------------------------------------
BTW, I suppose that the X11 apps from MacPorts should also by linked to this modified library.
Mr. Almighty Bbyer himself maintains our Xorg based X11 ports now ;-) So maybe he can chime in and advise...? In any case, I've been playing with X11 on Leopard lately but haven't been able to experience this functionality, if I unset the DISPLAY variable I simply can't open X11 programs from Terminal.app (even Apple provided ones under /usr/X11/bin); no launchd magic happens and all I get are "can't find display" errors (even though I do have a / tmp/launch-QLJ9Yh/\:0 sockect). Guess I need to look into the matter more thoroughly, I do have a highly customized environment after all. Regardless, I'll add the corrections to our X11 advise on install.php as soon as I get a chance. Regards,... -jmpp
On 2007-11-23 17:32:01 -0400, Juan Manuel Palacios wrote:
In any case, I've been playing with X11 on Leopard lately but haven't been able to experience this functionality, if I unset the DISPLAY variable I simply can't open X11 programs from Terminal.app
AFAIK, unsetting DISPLAY is an error if you want to use X clients, even Apple ones.
(even Apple provided ones under /usr/X11/bin); no launchd magic happens and all I get are "can't find display" errors (even though I do have a / tmp/launch-QLJ9Yh/\:0 sockect).
because DISPLAY is unset. DISPLAY needs to contain the name of the socket in some form. -- Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
On Nov 26, 2007, at 6:45 AM, Vincent Lefevre wrote:
On 2007-11-23 17:32:01 -0400, Juan Manuel Palacios wrote:
In any case, I've been playing with X11 on Leopard lately but haven't been able to experience this functionality, if I unset the DISPLAY variable I simply can't open X11 programs from Terminal.app
AFAIK, unsetting DISPLAY is an error if you want to use X clients, even Apple ones.
(even Apple provided ones under /usr/X11/bin); no launchd magic happens and all I get are "can't find display" errors (even though I do have a / tmp/launch-QLJ9Yh/\:0 sockect).
because DISPLAY is unset. DISPLAY needs to contain the name of the socket in some form.
-- Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/ blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS- Lyon)
The system should set DISPLAY=/tmp/launch_bla_bla_bla . All you need to do is remove any DISPLAY=0.0 lines in your ~/.profile and ~/.xinitrc. You might even try renaming ~/.xinitrc to ~/.xinitrc.old Do the above, quit X if it is running, then start some X app like gedit. X should start and then your app. If you check the env you should see that the system has set DISPLAY for you. William Davis frstanATbellsouthDOTnet Mac OS X.5.1 Darwin 9.1.0 Xquartz-1.2a11 Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non
On Nov 26, 2007, at 8:03 AM, William Davis wrote:
On Nov 26, 2007, at 6:45 AM, Vincent Lefevre wrote:
On 2007-11-23 17:32:01 -0400, Juan Manuel Palacios wrote:
In any case, I've been playing with X11 on Leopard lately but haven't been able to experience this functionality, if I unset the DISPLAY variable I simply can't open X11 programs from Terminal.app
AFAIK, unsetting DISPLAY is an error if you want to use X clients, even Apple ones.
(even Apple provided ones under /usr/X11/bin); no launchd magic happens and all I get are "can't find display" errors (even though I do have a / tmp/launch-QLJ9Yh/\:0 sockect).
because DISPLAY is unset. DISPLAY needs to contain the name of the socket in some form.
-- Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS- Lyon)
The system should set DISPLAY=/tmp/launch_bla_bla_bla . All you need to do is remove any DISPLAY=0.0 lines in your ~/.profile and ~/.xinitrc. You might even try renaming ~/.xinitrc to ~/.xinitrc.old Do the above, quit X if it is running, then start some X app like gedit. X should start and then your app. If you check the env you should see that the system has set DISPLAY for you.
I was trying all this and knew what value I had to set DISPLAY to, but I was actually looking into the magic by which the env variable is "automagically set for you by the system" (i.e. not requiring you to set it by hand to the launchd based ":0" socket path). So I tried unsetting my custom value and nothing happened, nothing replaced it so opening X11 programs didn't trigger X11.app to spring up to life. The key step I was missing was opening a new, fresh shell with no ~/.profile based setting of DISPLAY from the start; in that case the env variable was indeed set to the magic path and opening X11 programs did bring up X11.app automagically. I've added a very small text about this to install.php, omitting all the (I believe unnecessary) launchd details: "For Tiger and earlier only, add an appropriate X11 DISPLAY environment variable to run X11 dependent programs, as Leopard takes care of this requirement on its own." Feel free to suggest better wording or even a different sentence altogether -- I was falling asleep when I wrote that and haven't gotten around to reviewing it ;-) Regards,... -jmpp
participants (4)
-
Frank Rietta
-
Juan Manuel Palacios
-
Vincent Lefevre
-
William Davis