From owner-freebsd-hackers Mon Sep 18 19:10:21 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA23502 for hackers-outgoing; Mon, 18 Sep 1995 19:10:21 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA23472 for ; Mon, 18 Sep 1995 19:10:12 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id TAA09038 for hackers@freebsd.org; Mon, 18 Sep 1995 19:08:02 -0700 From: Terry Lambert Message-Id: <199509190208.TAA09038@phaeton.artisoft.com> Subject: SYSCONS PROBLEM IDENTIFIED To: hackers@freebsd.org Date: Mon, 18 Sep 1995 19:08:02 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 676 Sender: owner-hackers@freebsd.org Precedence: bulk About a week ago, someone was complaining that when an attribute bit was set and you cleared the screen, that the whole screen went to that attribute. Well, the problem is that the attribute state implys a fg/bg color state change; in reality, the fg/bg color state should be kept seperate from the attribute state, even if it implies a color state change. That is, the clear sreen/area/character operations on a console should take the color into account as if the attributes were at state 0 instead of using the altered color table. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.