From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <16ff6b980812241454r2ce20ff1g1e03c4dadeec832c@mail.gmail.com>
Date: Wed, 24 Dec 2008 23:54:57 +0100
From: "Mathieu Lonjaret" <lejatorn@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
In-Reply-To: <d5f128d9eadb8c65155ee6e39977b241@quanstro.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <3eba327b0b11e6729a74dec02056fe29@smgl.fr.eu.org>
	<d5f128d9eadb8c65155ee6e39977b241@quanstro.net>
Subject: Re: [9fans] fn oddity with acme
Topicbox-Message-UUID: 6f55c98a-ead4-11e9-9d60-3106f5b1d025

On Wed, Dec 24, 2008 at 7:04 PM, erik quanstrom <quanstro@quanstro.net> wrote:
>> I've defined such an rc function:
>> fn acmef { acme -f /lib/font/bit/fixed/unicode.8x13.font }
>> and when I call this function I keep getting this error displayed
>> repetively on the screen:
>>
>> grow segment 3 -> f00000 would overlap 0 [f000000-10000000]
>>
>> this happens both with p9p acme/rc and in 9vx.
>
> i can't replicate this behavior on linux.  i don't see how it could happen
> with p9p.
>
> any chance your font or some of the attendent images are
> broken?
>
> are you using the latest 9vx?  on what os?
>
> - erik

Ah sorry I had confused the various tests I did: the case where I
actually have this problem is if
I call the function acme itself, ie if I do
fn acme { acme -f /lib/font/bit/fixed/unicode.8x13.font }

If I call it acmef or whatever else, no problem, which seems less odd to me now.

Still, is that supposed to happen if I one uses for a function name
the one of a binary?

Mathieu