Re: [Xquartz-dev] XQuartz 2.6.1_rc1
Peter Dyballa wrote:
The final release has a strange habit: it launches an extra xterm! How can I stop it doing so?...
I'm not sure if this is related to your extra xterm. I noticed in 2.6.1_final seems to reset my plist, it reverted to the default which opens an xterm from launchd. I followed instructions in the user FAQ to make it go away: http://xquartz.macosforge.org/trac/wiki/X11-UsersFAQ. You can check if that's whats causing it with: defaults read org.macosforge.xquartz.X11 If needed, you can turn it off with: defaults write org.macosforge.xquartz.X11 app_to_run /usr/bin/true You may have already looked at this, just a thought. Dave
On Mar 23, 2011, at 17:27, Dave Ray wrote:
Peter Dyballa wrote:
The final release has a strange habit: it launches an extra xterm! How can I stop it doing so?...
I'm not sure if this is related to your extra xterm. I noticed in 2.6.1_final seems to reset my plist, it reverted to the default which opens an xterm from launchd. I followed instructions in the user FAQ to make it go away: http://xquartz.macosforge.org/trac/wiki/X11-UsersFAQ.
You can check if that's whats causing it with: defaults read org.macosforge.xquartz.X11
If needed, you can turn it off with: defaults write org.macosforge.xquartz.X11 app_to_run /usr/bin/true
It would be org.x.X11 for the Leopard version since on Leopard, it overrides the Apple-provided X11 and uses that identifier. There was certainly nothing intentional done to "reset" preferences or anything like that...
Am 24.03.2011 um 02:00 schrieb Jeremy Huddleston:
There was certainly nothing intentional done to "reset" preferences or anything like that...
It has an entry "app_to_run" = "/usr/X11/bin/xterm"; The entry "app_to_run" = "/opt/local/bin/xterm"; appears in org.macports.X11.plist. I'm pretty sure I never added this. And both files have pretty recent modification dates: -rw------- 1 pete pete 1519 24 Mär 01:04 ~/Library/Preferences/ org.macports.X11.plist -rw------- 1 pete pete 1477 23 Mär 23:51 ~/Library/Preferences/ org.x.X11.plist Again, I'm pretty sure that I did not make a change to any of them in months. -- Greetings Pete Time is an illusion. Lunchtime, doubly so.
On Mar 24, 2011, at 3:20 AM, Peter Dyballa wrote:
Am 24.03.2011 um 02:00 schrieb Jeremy Huddleston:
There was certainly nothing intentional done to "reset" preferences or anything like that...
It has an entry
"app_to_run" = "/usr/X11/bin/xterm";
The entry
"app_to_run" = "/opt/local/bin/xterm";
appears in org.macports.X11.plist. I'm pretty sure I never added this. And both files have pretty recent modification dates:
-rw------- 1 pete pete 1519 24 Mär 01:04 ~/Library/Preferences/org.macports.X11.plist -rw------- 1 pete pete 1477 23 Mär 23:51 ~/Library/Preferences/org.x.X11.plist
Again, I'm pretty sure that I did not make a change to any of them in months.
Those are the default values (and have been the default values) since Leopard 10.5.0 shipped. Check the FAQ that Dave just mentioned.
Am 24.03.2011 um 17:57 schrieb Jeremy Huddleston:
Those are the default values (and have been the default values) since Leopard 10.5.0 shipped.
Then all X servers on Leopard were faulty until X11-2.6.1 was released... -- Greetings Pete (: _ / __ - - _/ \__/_/ - - (´`) (´`) - - `´ `´
On Mar 24, 2011, at 10:35 AM, Peter Dyballa wrote:
Am 24.03.2011 um 17:57 schrieb Jeremy Huddleston:
Those are the default values (and have been the default values) since Leopard 10.5.0 shipped.
Then all X servers on Leopard were faulty until X11-2.6.1 was released...
I don't think so...
Am 24.03.2011 um 20:37 schrieb Jeremy Huddleston:
Then all X servers on Leopard were faulty until X11-2.6.1 was released...
I don't think so...
Before a week ago, or such, I never had this xterm... -- Greetings Pete Isn't vi that text editor with two modes... one that beeps and one that corrupts your file? – Dan Jacobson, on comp.os.linux.advocacy
On Mar 24, 2011, at 12:40 PM, Peter Dyballa wrote:
Am 24.03.2011 um 20:37 schrieb Jeremy Huddleston:
Then all X servers on Leopard were faulty until X11-2.6.1 was released...
I don't think so...
Before a week ago, or such, I never had this xterm...
If you start X11 by launching an application from Terminal.app (or otherwise trigger the launchd mechanism), X11.app won't run the initial xterm. If you launch X11 by launching X11.app directly, it will. This has been the case for years now.
Am 24.03.2011 um 21:01 schrieb Jeremy Huddleston:
If you start X11 by launching an application from Terminal.app (or otherwise trigger the launchd mechanism), X11.app won't run the initial xterm.
What is "launching an application from Terminal.app" and what is "otherwise trigger the launchd mechanism"? What is when I use a *shell* buffer in NS Emacs.app or "AppKit" Emacs.app?
If you launch X11 by launching X11.app directly, it will. This has been the case for years now.
How do I launch X11.app directly? Is this by clicking the X11.app icon in dock? (Doing this has been the case for years now.) Why do so many different methods of launching an application create so different results? In the end it's always launchd, similar to a shell in other UNIX systems, so why should this make a difference? What is the purpose behind this? Where is this all documented? -- Greetings Pete »¿ʇı̣ əsnqɐ ʇ,uɐɔ noʎ ɟı̣ ɓuı̣ɥʇʎuɐ sı̣ pooɓ ʇɐɥʍ«
On Mar 24, 2011, at 3:55 PM, Peter Dyballa wrote:
Am 24.03.2011 um 21:01 schrieb Jeremy Huddleston:
If you start X11 by launching an application from Terminal.app (or otherwise trigger the launchd mechanism), X11.app won't run the initial xterm.
What is "launching an application from Terminal.app" and what is "otherwise trigger the launchd mechanism"? What is when I use a *shell* buffer in NS Emacs.app or "AppKit" Emacs.app?
That would fall under "otherwise trigger the launchd mechanism"
If you launch X11 by launching X11.app directly, it will. This has been the case for years now.
How do I launch X11.app directly? Is this by clicking the X11.app icon in dock? (Doing this has been the case for years now.)
Yes.
Why do so many different methods of launching an application create so different results?
The only difference here is whether or not to launch that first xterm... that was done for compatibility reasons for people who expect that default xterm when they launch X11.app directly (like it happened on Tiger by default).
In the end it's always launchd, similar to a shell in other UNIX systems, so why should this make a difference? What is the purpose behind this? Where is this all documented?
There has been plenty of discussion about this in the xquartz-dev and x11-users mailing list ... mostly about 2 years ago... or you can always look through the ChangeLogs in git.
participants (3)
-
Dave Ray
-
Jeremy Huddleston
-
Peter Dyballa