From: Tom Culliton <culliton@clark.net>
To: rc@hawkwind.utcs.toronto.edu
Cc: john@loverso.southborough.ma.us, rsalz@osf.org
Subject: Re: Speaking of counting...
Date: Fri, 2 May 1997 18:09:14 -0400 [thread overview]
Message-ID: <199705022209.SAA16770@clark.net> (raw)
So far jot and seq have been mentioned, (every machine I have available
says "jot not found" though... and ditto seq) but no specifics,
I have been accused of wanting to reinventing the wheel, (exactly what
I was trying to avoid)
Scott has shared some perl code, (Euw! The evil anit-rc!) ;-) (Thank
you.)
I swear I've seen this in rc/awk before...
next reply other threads:[~1997-05-02 23:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-05-02 22:09 Tom Culliton [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-05-03 12:43 rsc
1997-05-03 7:57 Byron Rakitzis
1997-05-02 3:30 Rich Salz
1997-05-02 14:51 ` John Robert LoVerso
1997-05-01 21:40 Tom Culliton
1997-05-02 1:26 ` Scott Schwartz
1997-05-02 2:44 ` Charles M. Hannum
1997-05-02 5:52 ` Scott Schwartz
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=199705022209.SAA16770@clark.net \
--to=culliton@clark.net \
--cc=john@loverso.southborough.ma.us \
--cc=rc@hawkwind.utcs.toronto.edu \
--cc=rsalz@osf.org \
/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).