From owner-freebsd-questions@FreeBSD.ORG Wed Feb 23 21:31:04 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A54B016A4CE for ; Wed, 23 Feb 2005 21:31:04 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2679143D1F for ; Wed, 23 Feb 2005 21:31:04 +0000 (GMT) (envelope-from freebsdjunkie@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so6779wra for ; Wed, 23 Feb 2005 13:31:03 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=CMNnNpiLPlNCJ2Hxp/VPRayLiIGsf8H9sA6A6aYeoQkc4vYsmvi/N3r9Do3h+sXb5UdOMTbUzdTpfq4q4Xa7/qu0WGLmuJsPNTbMwK8bXb3LGMUn0vKjqKyNteS2bSv5XRy+ceV6yEa1EQfM2fiqnhGeV9WFkDtTGmaO6eOxRbc= Received: by 10.54.56.68 with SMTP id e68mr26963wra; Wed, 23 Feb 2005 13:31:03 -0800 (PST) Received: by 10.54.8.30 with HTTP; Wed, 23 Feb 2005 13:31:03 -0800 (PST) Message-ID: <32ab229c050223133148640a89@mail.gmail.com> Date: Wed, 23 Feb 2005 14:31:03 -0700 From: Gordon Freeman To: freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Eterm transparency problem. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Gordon Freeman List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Feb 2005 21:31:04 -0000 Is anyone else having a problem with Eterm 0.9.3? I love its transparency ability and had it set up with the following user.cfg: begin color foreground rgb:ff/ff/ff end begin attributes font fx none end begin image type background mode trans cmod image 100 end begin toggles itrans on buttonbar off xterm_select on end begin misc term_name xterm end Prior to the 0.9.3 update this shaded the terminal window a little less than 50%. Now it shades it a blue tint. Trying just the --O and --shade options yields identical results. However, if I don't use transparency the --shade option works correctly. Anyone seen a similar error? Slight tangent question: Is emailing the maintainer the only way to report a bug to a port? The FreeBSD PR system looks like it isn't intended for ports.