🚀 go-pugleaf

dworkin@village.org writes:

> I'm not too familiar with X on a LispM (I've got Genera 5.something on
> my 3640, and never have gotten the networking world functional).
> However, I can intuit some bits from general knowledge:
> 
> "bzero" is a C function that zeroes a block of memory.  I doubt
> seriously that the X server only calls it in the context of printing
> out error messages - most likely, that's just the first place it's
> trying to invoke it, and failing.  The other symptoms you describe
> would imply that the server is completely going away at about the same
> time as this error is reported.

No, the server is not going away. I can do Start X Screen TRILOGY and
if the server hasn't been started yet then I get the message "Error:
The X server is not running." and I go into the debugger. If the
server is running and I do Start X Screen TRILOGY then the status line
says "CLX Input" and the listener is like an xterm that has started a
new process without forking it to the background; the curser hangs and
keystrokes don't do anything but you can use the Select key to move to
another listener or wherever and Function-Abort will restore the
command prompt.

I feel like like I'm close to getting things to work.... The X Server
stuff is incredibly under-documented. For example, there is no
documentation of the keyword arguments to the Start X Server command
such as :Hostile (other than "Hostile takeover", whatever that means),
and the full DocEx documentation for Start X Server Command is
"Creates a background process to manage X network connections." It
does not seem to be "managing the connections" though....

Christopher