Date: Wed, 3 May 1995 19:05:43 -0500 (CDT) From: Peter da Silva <peter@bonkers.taronga.com> To: terry@cs.weber.edu (Terry Lambert) Cc: hackers@FreeBSD.org Subject: Re: Screen print capability Message-ID: <199505040005.TAA17949@bonkers.taronga.com> In-Reply-To: <9505031625.AA13099@cs.weber.edu> from "Terry Lambert" at May 3, 95 10:25:14 am
next in thread | previous in thread | raw e-mail | index | archive | help
> It's not an SCO console if it doesn't allow the character set shifting, > doesn't allow scan-code mode operation, doesn't support escape sequence > reporting, doesn't support switching the character attribute between > blink and high intensity for background colors, doesn't support ISO > and SCO color selection escape sequences, or doesn't support scrolling > when the 80th column/25th line character is written (the proper way to > handle it is to remember the 79th character, draw the 80th at the 79th > position, insert a character at the 79th making the 79th the 80th, and > redrawing the 79th). I didn't see screen printing in that list, but if it's critical for SCO apps then turn it on for SCO apps, but leave it off by default. > Leaving out a feature because you find it morally repugnant isn't an > option. There's a nice, clear "yes/no" line for compatability, and that > would put you firmly on the "no" side. OK, do you plan to support Xenix 286 emulation? If compatibility is a yes/no matter then leaving that out puts you clearly on the "no" side. That means you need to support Xenix shared memory and Xenix semaphores, which use special files in the file system. No, I don't expect that (though it *would* be a killer app... we're keeping a bevy of Xenix boxes alive for legacy support), but it does mean that SCO compatibility isn't a nice, clear "yes/no" line after all.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505040005.TAA17949>