From: matt <matt@proweb.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] text utility
Date: Thu, 24 Jul 2003 10:19:53 +0100 [thread overview]
Message-ID: <3F1FA4B9.6090209@proweb.co.uk> (raw)
In-Reply-To: <200307231842.h6NIgk723821@augusta.math.psu.edu>
Dan Cross wrote:
>Why not use the definition of the tac utility that used to be
>distributed with BSD Unix? I think it printed out lines in reverse
>order (similar to tail -r). Something to print out all the bytes in a
>file in reverse order might be useful, though. Currently, I can't
>think why.
>
> - Dan C.
>
to see what interesting UTF-8 comes out of course
next prev parent reply other threads:[~2003-07-24 9:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 11:45 pac
2003-07-21 11:52 ` boyd, rounin
2003-07-22 14:09 ` rog
2003-07-22 14:35 ` boyd, rounin
2003-07-22 16:43 ` rog
2003-07-22 23:28 ` Geoff Collyer
2003-07-23 15:05 ` rog
2003-07-23 18:42 ` Dan Cross
2003-07-24 9:19 ` matt [this message]
2003-07-28 8:47 ` Ralph Corderoy
2003-07-28 21:58 ` Geoff Collyer
2003-07-30 8:25 ` Ralph Corderoy
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=3F1FA4B9.6090209@proweb.co.uk \
--to=matt@proweb.co.uk \
--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).