From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <327536b0b8212e3b29f8e09922dcf3c8@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] awk, not utf aware...
From: erik quanstrom <quanstro@quanstro.net>
Date: Thu, 28 Feb 2008 17:08:26 -0500
In-Reply-To: <5d375e920802281348h59578a70g6023db65dc4d8068@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 6852dac0-ead3-11e9-9d60-3106f5b1d025

> I thought it was obvious that the output was from a 'standard' Plan 9
> terminal. But given the percentage of people actually using plan9 in
> this list, I guess I should have been much more explicit.
>
> And the problem is precisely that the environment under which awk run
> commands is completely different from the one awk is run in; in other
> words, awk spreads its 'simian' (ape-ish) nature.

i think that awk is in a no-win situation here.  if it used rc, then
awk scripts from plan 9 would break on unix and vice versa.  sam and
acme have similar issues in p9p's environment.  i don't see how either
using the native shell or using the shell from the original
environment is wrong a priori.  awk picks a lane and sticks too it.
i'd bet that benefits other ape stuff like lp.

if you really don't like this situation, perhaps the solution is to
improve upon awk.  a plan 9 scripting language based on sre's --- as
suggested by rob --- could be really cool.

- erik