From owner-freebsd-hackers Thu Nov 20 17:45:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA29921 for hackers-outgoing; Thu, 20 Nov 1997 17:45:37 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.5.85]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA29906 for ; Thu, 20 Nov 1997 17:45:31 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.7/8.8.7) id SAA08710; Thu, 20 Nov 1997 18:45:30 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd008696; Thu Nov 20 18:45:22 1997 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id SAA19629; Thu, 20 Nov 1997 18:45:20 -0700 (MST) From: Terry Lambert Message-Id: <199711210145.SAA19629@usr05.primenet.com> Subject: Re: vidcontrol questions To: jbryant@unix.tfs.net Date: Fri, 21 Nov 1997 01:45:20 +0000 (GMT) Cc: tlambert@primenet.com, freebsd-hackers@freebsd.org In-Reply-To: <199711210036.SAA11620@unix.tfs.net> from "Jim Bryant" at Nov 20, 97 06:36:09 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > What does reverse video mean? What does underline mean? > [snip] > > terry, > > user_default and kernel_default were provided for the purpose the > gentleman asked about. > > vidcontrol only operates on the console, thus the question was > concerning the console. > > there is no need to mung up termcap by giving nonstandard definitions > for standard items. > > also, check case 'm': in syscons.c... i believe it does follow the > SCO standard for changing colors seperately from the attributes you mention. Yah. The point is that you aren't talking colors when you use "sticky" values for these things. He's confused sticky and non-sticky in his expectations, so the real bug is not in the software. As far as not hacking termcap: This presumes you are using the color console as a monochrome console, but with different definitions of "default", "reverse", "underline", "blink", "bold", and whatever other attributes you pretend to accept (ie: double wide, double high and wide, top half, double wide and high bottom half, etc.). If you want to use it as a color terminal, you shouldn't depend on "sticky" defaults. For example, how does a particular set of "sticky" defaults interact with colorls (answer: badly), and so on. So setting defaults is kind of mutually exclusive with treating it as a color console... if I select a foreground color of green in my color aware application, I'm pretty much screwed if the user has selected a "default backgound color" of green as well. I have no way of knowing this, as a color aware application. The SCO "setcolor" utility was really meant for changing defaults for monochrome-only aware apps. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.