From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <dd6fe68a0812270904h5ee2bb9eg417c5bb6f2ee0c6a@mail.gmail.com>
Date: Sat, 27 Dec 2008 09:04:55 -0800
From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] fn oddity with acme
In-Reply-To: <16ff6b980812250316l1471557ax79ab367c7942a09e@mail.gmail.com>
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>
	 <16ff6b980812250316l1471557ax79ab367c7942a09e@mail.gmail.com>
Topicbox-Message-UUID: 724b976e-ead4-11e9-9d60-3106f5b1d025

>> fn acme { builtin acme -f /lib/font/bit/fixed/unicode.8x13.font $*}
>
> 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.

I doubt that "builtin acme" was a planned feature of rc,
though it's a neat trick.  If you want to be clearer, you
could write /bin/acme.

Russ