From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: [9fans] native awk
Date: Mon, 4 Mar 2013 00:22:28 +0000 [thread overview]
Message-ID: <2c3a55e9921e2c63c18c47d0f0511ea6@quintile.net> (raw)
My 2¢ on the subject of native awk.
The only "native" features I have wanted are:
utf-8 clean - honestly I don't know if it is
alreay but my suspicion is that it is not.
an input parsing mode which respects rc tokenizing rules,
this would make things like du -a | awk more reliable in the
face of weird filenames.
-Steve
next reply other threads:[~2013-03-04 0:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 0:22 Steve Simon [this message]
2013-03-04 2:47 ` 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=2c3a55e9921e2c63c18c47d0f0511ea6@quintile.net \
--to=steve@quintile.net \
--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).