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
Date: Sat, 27 Dec 2008 09:04:55 -0800 [thread overview]
Message-ID: <dd6fe68a0812270904h5ee2bb9eg417c5bb6f2ee0c6a@mail.gmail.com> (raw)
In-Reply-To: <16ff6b980812250316l1471557ax79ab367c7942a09e@mail.gmail.com>
>> 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
next prev parent reply other threads:[~2008-12-27 17:04 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
2008-12-25 11:16 ` Mathieu Lonjaret
2008-12-27 17:04 ` Russ Cox [this message]
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=dd6fe68a0812270904h5ee2bb9eg417c5bb6f2ee0c6a@mail.gmail.com \
--to=rsc@swtch.com \
--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).