[Xquartz-dev] 2.3.2_rc4

[Nicholas Riley]

On Fri, Dec 19, 2008 at 08:17:12AM +0100, Martin Costabel wrote:
> Cameron Simpson wrote:
> >On 19Dec2008 00:37, Martin Costabel <costabel at wanadoo.fr> wrote:
> >>I think the following works (does for me, anyway, but I haven\t tested  
> >>it extensively):
> >>
> >>#!/bin/sh
> >>/usr/bin/login -pqf $USER <<EOF
> >>  $*
> >>EOF
> >
> >Please no. That completey mangles the command line if any of the
> >app command line arguments have spaces.
> 
> Which app command line arguments are you talking about? I am targeting 
> specifically the startup procedure of X11 on Mac OS X Leopard, where the 
> command corresponding to $* in the above is typically something like
> 
>   /Applications/Utilities/X11.app/Contents/MacOS/X11.bin -psn_0_716975

I guess one possibility may be if the user moves X11.app somewhere
else aside from /Applications/Utilities.  Also, it is possible as of
10.5 to use the Launch Services API to pass command-line arguments to
a GUI app.  I don't know of any reason you'd want to in this case, but
it is a possibility.  At least the first should be easy to test by
just moving X11.app to a directory with a space in it.

> The current version in 2.3.2-rc4 is a regression for tcsh users, because 
> it not only does not run a login shell in the first xterm it starts, but 
> it does not transmit a login environment to the commands started from 
> X11's "Applications" menu.

The same is true for zsh, as I mentioned in my original email.

> >Are we not spending a lot of effort in the wrong place?
> 
> That may well be the case, but I don't see anyone spending any effort on 
> rewriting once again the whole startup procedure for X11 on Leopard.

It seems the startup procedure has already been rewritten about 4
times :-)

-- 
Nicholas Riley <njriley at uiuc.edu> | <http://www.uiuc.edu/ph/www/njriley>