From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@coraid.com>
Date: Fri, 27 Feb 2009 13:52:55 -0500
To: 9fans@9fans.net
Message-ID: <da1daea7951d03838230b1a75367934e@coraid.com>
In-Reply-To: <509071940902271045y34b1bcfcxc03169445bccb85f@mail.gmail.com>
References: <138575260902260858j58dfd1cdq9debb9637340a7c8@mail.gmail.com>
	<13426df10902270845o142ad949lb904b3b7b7e918a9@mail.gmail.com>
	<138575260902270926m6e229afr7acafa812597a750@mail.gmail.com>
	<509071940902271045y34b1bcfcxc03169445bccb85f@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Acme huge bar
Topicbox-Message-UUID: a9dd8250-ead4-11e9-9d60-3106f5b1d025

> IIRC, acme tries to move the tag bar a line at a time, but does so
> using the sizes of your tag bar font (-f). you'll see this behavior
> occurs because the different heights on the fonts mean you can't
> satisfy both of them with whole-row-only moves. acme won't ever
> display part of a line of text.
>
> doesn't address whether the gap should be black or not, but that's why
> it exists.

i don't understand why different fonts would cause this.
why is there need for slop in the tag?  one doesn't need
any relationship between the tag text and the frame text
so all the slop can be eliminated from the tag and added
to the frame.

- erik