From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <9632fafebd0cd1b4aa9e3f85b8f3d4fe@quanstro.net>
To: 9fans@9fans.net
From: erik quanstrom <quanstro@quanstro.net>
Date: Wed, 24 Dec 2008 19:55:18 -0500
In-Reply-To: <16ff6b980812241454r2ce20ff1g1e03c4dadeec832c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] fn oddity with acme
Topicbox-Message-UUID: 6f5b5206-ead4-11e9-9d60-3106f5b1d025

> 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.

i think you wish

fn acme { builtin acme -f /lib/font/bit/fixed/unicode.8x13.font $*}

you ran out of stack space.

- erik