Re: 2.1.1 and xterm
Re: 2.1.1 and xterm
- Subject: Re: 2.1.1 and xterm
- From: William Davis <email@hidden>
- Date: Fri, 14 Dec 2007 00:55:16 -0500
On Dec 13, 2007, at 8:48 PM, Chip Griffin wrote:
On Dec 13, 2007, at 01:08, Jeremy Huddleston wrote:
On Dec 12, 2007, at 20:12, Chip Griffin wrote:
OK. How about for consistencies sake if we go back to having it
controlled by .xinitrc!
No. You're missing the point. When the server starts, no
applications run (except quartz-wm).
I guess. Truly I am beginning to think someone changed my native
tongue because we seem to be having a lot of trouble communicating.
This is not the behavior I am seeing. When the server starts, Xterm
starts even though it is not mentioned in my .xinitrc. The only
thing executed in my .xinitrc file is quartz-wm (aside from resource
management stuff). See below for my actual .xinitrc.
If it ain't there it should not start.
Right, it doesn't.
This is not the behavior I'm seeing, nor are others from what I can
tell.
There ya go, consistent with previous behavior. User controllable.
Best of both worlds.
It is consistent "with both worlds". Launching X11.app from the
dock or running 'open -a X11' just runs xterm (or whatever you have
for app_to_run). That's all. Yes, maybe it should've been called
Xterm.app, but it's not. This was a good decision made by Apple to
integrate with launchd.
If you want to launch the X server by hand and don't want any
application to start, then set app_to_run to /usr/bin/true.
Simple. Consistency with old behavior. Compatibility with other
software. Options to change what you want.
But how is this consistent? It doesn't follow the behavior in the
old regime where X11 would only execute those items called out in
the system xinitrc or the personal .xinitrc. I understand that there
is a method to control it, but it is new and therefore not
consistent. In the old regime I, as a power user, could edit
the .xinitrc and change the behavior from the default (launch xterm)
to the desired (whatever that might be, launch other wm, launch
other programs, etc). Now I can somewhat do that, but the
methodology is completely different (edit some plist somewhere,
which is definitely not unix-like but rather distinctly Mac-like).
So it sounds to me like the only two ways to launch exclusively the
X app I want (and no other) is to either (a) launch the X app from a
terminal window (such as Terminal.app) or (b) edit the plist where
app_to_run is mentioned. OK, I can do that. But let's not call it
consistent because it's not how we did things in the past. It's a
change. Change is good when it's warranted. As hard as you're
defending it I can guess that there are some strong reasons for it.
I have studied programming on and off over the years, but a
programmer I am not, so I will take it at face value.
Let me take a step back from previous comments and be 100% clear
here. I am tremendously grateful for the efforts of Jeremy, Ben, and
all the others who work to make X11, Xquartz, and the other pieces
of the puzzle work. Paid or volunteer, your efforts are applauded.
My comments above are not meant to stir controversy or irritate but
rather are an effort to understand and clarify how and why things
work the way they do.
Thanks.
-- Chip
#!/bin/sh
userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap
# merge in defaults and keymaps
if [ -f $sysresources ]; then
xrdb -merge $sysresources
fi
if [ -f $sysmodmap ]; then
xmodmap $sysmodmap
fi
if [ -f $userresources ]; then
xrdb -merge $userresources
fi
if [ -f $usermodmap ]; then
xmodmap $usermodmap
fi
exec quartz-wm
please look and see if you have the file /etc/xinit/xinitrc and if it
has the line
xterm &
toward the tail. This is the Tiger X11 init file. On my system it is
not present, having been moved to
/etc/X11.AppleBackup/xinit/xinitrc
it is not required to have a system xinitrc file (nor a ~/.xinitrc for
that matter) AFAICT since all that is set via launchd and the plists.
I suspect your old Tiger system xinitrc is still there and is starting
xterm.
Just a guess but only takes a minute to check. :)
William Davis
frstanATbellsouthDOTnet
Mac OS X.5.1 Darwin 9.1.0
X11.app 2.1.1 - (xorg-server 1.3.0-apple5)
Mac Mini Intel Duo @ 1.86 GHz
Mundus vult decepi, ego non
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden