From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@9fans.net
Subject: Re: [9fans] rc niggle, and proposed fix
Date: Wed, 22 Jun 2011 17:02:09 +0100 [thread overview]
Message-ID: <0d34ca37980c4db0a99135f256c7d8aa@terzarima.net> (raw)
In-Reply-To: <e80a8eedbc8aa7f3bc9ccdbdf9870d51@ladd.quanstro.net>
>ifs seems a holdover. it's only ever used in `{} yet
>it's a global inherited variable. so it's easy to write
>a script that assumes that ifs is set to the default.
i wonder if it's best left alone. it isn't detailed enough
to crack many plausible formats, for instance full csv.
if i needed one of those formats to feed into a `{} i'd add
a filter that converted to quoted & space-separated fields
that the default ifs would crack.
next prev parent reply other threads:[~2011-06-22 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 19:48 erik quanstrom
2011-06-22 16:02 ` Charles Forsyth [this message]
2011-06-22 16:21 ` 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=0d34ca37980c4db0a99135f256c7d8aa@terzarima.net \
--to=forsyth@terzarima.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).