Start X11 automatically when launching programs from Terminal

[Leo Singer]

On May 16, 2013, at 9:29 PM, Jeremy Huddleston Sequoia <jeremyhu at apple.com> wrote:

> 
> On May 16, 2013, at 8:45 PM, Leo Singer <aronnax at macports.org> wrote:
> 
>> On May 16, 2013, at 8:12 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
>> 
>>> 
>>> On May 16, 2013, at 22:00, Leo Singer wrote:
>>> 
>>>> I don't know how they differ. I do notice that there is the line:
>>>> 
>>>> system "launchctl load /Library/LaunchDaemons/org.macports.privileged_startx.plist"
>>>> 
>>>> in the port's post-activate stage. What does that do? Could the port also do:
>>>> 
>>>> system "launchctl load -w /Library/LaunchAgents/org.macports.startx.plist"
>>>> 
>>>> ?
>>> 
>>> No it couldn't because launchagents are per-user processes launched at login, whereas launchdaemons are pre-computer processes launched at system startup. Each user needs to start the launchagents themselves if they want them.
>> 
>> Ah... which is why this can't be done with 'port load' either, because 'port load' handles launchdaemons.
>> 
>> Is it really just the patchfile https://trac.macports.org/browser/trunk/dports/x11/xinit/files/disable-launchagent.patch that disables on-demand loading of X11.app by default?
> 
> Yes.
> 
> This approach was taken because X11.app shipped before some Snow Leopard 10.6.3 would not work correctly if $DISPLAY belonged to another server.  This is also why the XQuartz package requires 10.6.3 to install.
> 
> It might be worth revisiting this and perhaps just disabling it on Leopard.

Yes, please! It would be really nice if the MacPorts X11.app started automatically on Mountain Lion, without any further user intervention.