[Xquartz-dev] 2.3.2_rc4

[Harald Hanche-Olsen]

+ Nicholas Riley <njriley at uiuc.edu>:

> It's also the magic number for Mach-O binaries, which is more 
> likely than Java class files in this case.

So what is clearly happening, then, is that some shell is being run 
with a binary as its presumed script. Going back in the thread ...

+ Martin Costabel <costabel at wanadoo.fr>:

>> Dec 20 01:11:47 mbookp [0x0-0x62062].org.x.X11[1524]: Warning: no 
>> access to tty (Bad file descriptor).
>> Dec 20 01:11:47 mbookp [0x0-0x62062].org.x.X11[1524]: Thus no job 
>> control in this shell.
>> Dec 20 01:11:47 mbookp [0x0-0x62062].org.x.X11[1524]: 
>> \312\376\272\276^B^G^C^P^Z\2120^L^R: Command not found.

Those messages appear to come from (t)csh ...

OH! (Slaps forehead) Now I see it ... more recently, Martin wrote

+ Martin Costabel <costabel at wanadoo.fr>:

> I did. As I wrote when I reported this first, I used the wrapper 
> script with the ~/.x11run hook (which comes from you, as I see 
> now), and placed Peter's script
>
>> #! /bin/bash
>> exec -l "$SHELL" "$@"
>
> into ~/.x11run.

Yeah, but that is wrong usage of .x11run, since the arguments (i.e., 
$@) are: First the path to X11.bin, then arguments meant for X11.bin. 
Of course this makes your login shell try to run X11.bin as a script.

- Harald