From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <16ff6b980812250316l1471557ax79ab367c7942a09e@mail.gmail.com> Date: Thu, 25 Dec 2008 12:16:16 +0100 From: "Mathieu Lonjaret" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> In-Reply-To: <9632fafebd0cd1b4aa9e3f85b8f3d4fe@quanstro.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <16ff6b980812241454r2ce20ff1g1e03c4dadeec832c@mail.gmail.com> <9632fafebd0cd1b4aa9e3f85b8f3d4fe@quanstro.net> Subject: Re: [9fans] fn oddity with acme Topicbox-Message-UUID: 705ed178-ead4-11e9-9d60-3106f5b1d025 On Thu, Dec 25, 2008 at 1:55 AM, erik quanstrom wrote: >> 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 Ah thanks, I would have never thought of using builtin in that case, I thought that the word following builtin had to be an rc built-in command. Cheers, Mathieu -- GPG key on subkeys.pgp.net: KeyID: | Fingerprint: 683DE5F3 | 4324 5818 39AA 9545 95C6 09AF B0A4 DFEA 683D E5F3