Re: Command line arguments to the Xserver (XQuartz)?
Re: Command line arguments to the Xserver (XQuartz)?
- Subject: Re: Command line arguments to the Xserver (XQuartz)?
- From: Lars-Johan Liman <email@hidden>
- Date: Sat, 14 Jan 2012 11:22:29 +0100
email@hidden:
> Yeah, I think it respects some command line arguments, which you can
> pass "if you know what you're doing,"
(I think I do (famous last words ... ;-) ;-), although I must admit
that classic BSD is more of my home turf so I do run into surprises with
MacOS X from time to time ...)
> but that's not really supported.
All right ... but ... it also seems not to work.
XQuartz was heavily based on Xorg (right?), and I can even see the
command line argument strings in the server binary, e.g.,
$ strings - /Applications/Utilities/XQuartz.app/Contents/MacOS/X11.bin \
| grep -e -retro
-retro start with classic stipple and cursor
-retro
-retro start with classic stipple and cursor
-retro
but "/Applications/Utilities/XQuartz.app/Contents/MacOS/X11.bin -retro"
still gives me a black screen. (Yes, all X11 stuff unloaded from
launchd, and starting the program from command line is just a way of
debugging, by eliminating all the "misleading interference" ;-) from all
the startup scripts. I understand that the proper way of passing command
line arguments is from launchd.plist.)
This is either a simple bug, or it means that someone has put efforts
into removing (or navigating around) the code that parses the command
line.
... or it means that I've musunderstood the design entirely, which is
quite plausible, and in which case I will happily be enlightened. :-)
> If there's something you want to change, there's probably something
> you can set in NSDefaults instead, and if not, ask me and I can
> probably get it into the next release ;)
:-) That's a kind offer. I realise that one might want to move from
parsing command line options to using NSDefaults instead, and not have
to do both, but in that case I would really like to see all the classic
Xorg command line options as options in NSDefaults. They are there
because someone has wanted to use them somewhere, and losing the
flexibility would be and unfortunate step, I believe.
I'm toying with the idea to checkout the code and take a look at it
myself. That usually ends in disaster, but that never stops me from
trying. :-) If you could help me to take a shortcut in that process, by
indicating in which file the options parsing happens, that would be
appreciated.
> If you really want to do this, you can edit the LaunchAgent's
> launchd.plist and add those as arguments to startx. You'll need to
> logout and log back in to have these changes take effect.
Understood.
> You shouldn't need to pass a specific display to use (ie :8) because
> that is chosen for you automatically by startx.
(That was just an example.)
> There was a bug in 2.7.0 that forced it to use :0, but that is fixed
> in 2.7.1_rc1. If that's the reason you are trying to do this, just
> update to the rc.
(I'm already at the rc.)
... and most of all: Thanks for keeping X11 alive on the Mac!
Cheers,
/Liman
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden