From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <509071940902271045y34b1bcfcxc03169445bccb85f@mail.gmail.com>
References: <138575260902260858j58dfd1cdq9debb9637340a7c8@mail.gmail.com>
	<13426df10902270845o142ad949lb904b3b7b7e918a9@mail.gmail.com>
	<138575260902270926m6e229afr7acafa812597a750@mail.gmail.com>
	<509071940902271045y34b1bcfcxc03169445bccb85f@mail.gmail.com>
Date: Sat, 28 Feb 2009 18:45:19 +0100
Message-ID: <138575260902280945g184695ebi109591b9a5e0856c@mail.gmail.com>
From: hugo rivera <uair00@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Acme huge bar
Topicbox-Message-UUID: aa521340-ead4-11e9-9d60-3106f5b1d025

yes, I execute Font for each window I want to.
OK, got the point, thanks.

2009/2/27 Anthony Sorace <anothy@gmail.com>:
> do you do that by executing Font in each window?
>
> 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.
>
>



--
Hugo