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...
Date: Thu, 28 Feb 2008 22:48:07 +0100 [thread overview]
Message-ID: <5d375e920802281348h59578a70g6023db65dc4d8068@mail.gmail.com> (raw)
In-Reply-To: <200802281854.m1SIsg2m004288@skeeve.com>
> > % 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
next prev parent reply other threads:[~2008-02-28 21:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 18:54 Aharon Robbins
2008-02-28 21:48 ` Uriel [this message]
2008-02-28 22:08 ` erik quanstrom
-- strict thread matches above, loose matches on Subject: below --
2008-02-28 15:10 erik quanstrom
2008-03-03 23:48 ` Jack Johnson
2008-03-04 0:13 ` erik quanstrom
2008-02-27 9:57 erik quanstrom
2008-02-26 12:18 Gorka Guardiola
2008-02-26 13:16 ` Martin Neubauer
2008-02-26 14:54 ` Gorka Guardiola
2008-02-26 20:24 ` erik quanstrom
2008-02-26 21:08 ` geoff
2008-02-26 21:21 ` Pietro Gagliardi
2008-02-26 21:24 ` erik quanstrom
2008-02-26 21:32 ` Steven Vormwald
2008-02-26 21:40 ` Pietro Gagliardi
2008-02-26 21:42 ` Pietro Gagliardi
2008-02-26 23:59 ` Steven Vormwald
2008-02-27 2:38 ` Joel C. Salomon
2008-02-29 17:00 ` Douglas A. Gwyn
2008-02-26 21:34 ` erik quanstrom
2008-02-27 7:36 ` Gorka Guardiola
2008-02-27 15:54 ` Sape Mullender
2008-02-27 20:01 ` Uriel
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=5d375e920802281348h59578a70g6023db65dc4d8068@mail.gmail.com \
--to=uriel99@gmail.com \
--cc=9fans@cse.psu.edu \
/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).