From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] fn oddity with acme
Date: Wed, 24 Dec 2008 19:55:18 -0500 [thread overview]
Message-ID: <9632fafebd0cd1b4aa9e3f85b8f3d4fe@quanstro.net> (raw)
In-Reply-To: <16ff6b980812241454r2ce20ff1g1e03c4dadeec832c@mail.gmail.com>
> 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
next prev parent reply other threads:[~2008-12-25 0:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-24 17:50 Mathieu
2008-12-24 18:04 ` erik quanstrom
2008-12-24 22:54 ` Mathieu Lonjaret
2008-12-25 0:55 ` erik quanstrom [this message]
2008-12-25 11:16 ` Mathieu Lonjaret
2008-12-27 17:04 ` Russ Cox
2008-12-27 19:09 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9632fafebd0cd1b4aa9e3f85b8f3d4fe@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).