From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Either bug in the man page or in getfields
Date: Fri, 25 Oct 2002 02:21:48 -0700 [thread overview]
Message-ID: <29715c6cec5b286e9f652454f3a1e2ec@collyer.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 67 bytes --]
Re-read your message carefully. "gettokens" is not "getfields".
[-- Attachment #2: Type: message/rfc822, Size: 1768 bytes --]
From: Saroj Mahapatra <saroj@optonline.net>
To: 9fans@cse.psu.edu
Subject: [9fans] Either bug in the man page or in getfields
Date: Fri, 25 Oct 2002 09:04:03 GMT
Message-ID: <6d3220b4.0210241712.225164d6@posting.google.com>
getfields does not evaluate quotes, but tokenize does. Yet the man
page says: "Tokenize is gettokens with delims set to "\t\r\n ". Is
there a bug in getfields or is it a documentation bug?
Thank you,
Saroj Mahapatra
P.S. My two earlier messages mysteriously disapperared.
next reply other threads:[~2002-10-25 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 9:21 Geoff Collyer [this message]
2002-10-28 9:58 ` Saroj Mahapatra
-- strict thread matches above, loose matches on Subject: below --
2002-10-25 9:04 Saroj Mahapatra
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=29715c6cec5b286e9f652454f3a1e2ec@collyer.net \
--to=geoff@collyer.net \
--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).