From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <5d375e920802281348h59578a70g6023db65dc4d8068@mail.gmail.com>
Date: Thu, 28 Feb 2008 22:48:07 +0100
From: Uriel <uriel99@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] awk, not utf aware...
In-Reply-To: <200802281854.m1SIsg2m004288@skeeve.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <200802281854.m1SIsg2m004288@skeeve.com>
Topicbox-Message-UUID: 684cfcfe-ead3-11e9-9d60-3106f5b1d025

>  > %  echo |awk '{print |"echo $KSH_VERSION"}'
>  > @(#)PD KSH v5.2.14 99/07/13.2
>
>  Why is this broken?  If the shell that awk is running is PDKSH, or
>  KSH_VERSION exists in the environment, this is to be expected.

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.

uriel