From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <5b30be55a08595012f5b35ca53a9390f@quintile.net> From: "Steve Simon" Date: Mon, 24 Sep 2007 13:18:37 +0100 To: 9fans@cse.psu.edu Subject: Re: [9fans] Re: X Window System In-Reply-To: <1190632968.394008.109110@n39g2000hsh.googlegroups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: c3a2e812-ead2-11e9-9d60-3106f5b1d025 > Yes, I know that the port exists and it is running inside rio, isn't > it? it runs inside rio if you start it inside rio, start it instead of rio and it will use the whole display (as would acme, sam or catclock :-). > You can't compile it nowadays: I last compiled it against the 3rd edition but this should not make any real difference; from memory the only real changes in the compiler since then are the option of link time type checking and improvements to 64bit int support. I suggest you explore the 'incompatible type: "VOID" for op "DOT"' error, it may simply be somthing in your ape environment is not set up as x11 needs, (though it may be somthing less tractable of course). The biggest problem with this package is the limited plan9 driver - only 8bit pixmaps are supported and use on plan9 displays with depths other than 8bits is very slow. This could be fixed but it would probably be more sensible to update the port to the current X11 release. -Steve