From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Message-id: <E506B5D9-0C99-4A00-AAD1-91C4AD1DF75F@mac.com>
From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
In-reply-to: <6d14dc3a384b1cce44f440d0d4e854d9@terzarima.net>
Date: Mon, 30 Jun 2008 13:26:48 -0400
References: <6d14dc3a384b1cce44f440d0d4e854d9@terzarima.net>
Subject: Re: [9fans] sad commentary
Topicbox-Message-UUID: ceaf28e6-ead3-11e9-9d60-3106f5b1d025

I do this:

	fn build {
		8c $1^.c && 8l -o $1 $1^.8 && rm $1^.8
	}
	acmef sieve.c # acmef opens acme with fixed-width font in one column
	build sieve
	sieve 2053

when I need to build a one-file program.

That's another good argument against Plan 9 that Unix users can make:
why do I have to run two programs to compile a C source code file when
Unix needed only one? I've grown used to it - build and mk help.

On Jun 30, 2008, at 11:36 AM, Charles Forsyth wrote:

>>> For example the
>>> role of make as an equivalent for cc is not self-evident for a
>>> traditional normal OS-user.
>
>> come again?
>
> i thought it meant that he always types in cc commands on unix.
> of course you could do that too with 8c/8l but normally on plan 9 i
> create a mkfile except for the tiniest one-off things.
>