From: ron@ronnatalie.com (Ronald Natalie)
Subject: [TUHS] Command-line options
Date: Sat, 26 Mar 2016 16:54:48 -0400 [thread overview]
Message-ID: <4B49E73B-51BD-4834-AA8C-5F9F74BA784E@ronnatalie.com> (raw)
In-Reply-To: <CAC20D2OKN=emm+cJxDKez19JZKwFoa7C7TbfyNtbGf7_7eu=2w@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
More strictly, UNIX doesn’t have “type” in a file. They’re just a bunch of bytes. It’s up to whoever is making the file to decide if the name conveys that information or a magic number does.
The other fun character set was the old UNIVAC Fielddata. There were no non printing characters and in fact not even a null value (the 0 value was called master space and printed as @).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2284 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160326/5790c88f/attachment.bin>
next prev parent reply other threads:[~2016-03-26 20:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 14:43 [TUHS] Is the Teletype the unsung hero of Unix? Aharon Robbins
2016-03-25 19:47 ` Jaap Akkerhuis
2016-03-25 21:03 ` Diomidis Spinellis
2016-03-28 20:12 ` scj
2016-04-01 14:06 ` Dave Horsfall
2016-04-01 22:41 ` Greg 'groggy' Lehey
2016-03-25 21:29 ` [TUHS] Command-line options Warren Toomey
2016-03-25 23:25 ` Greg 'groggy' Lehey
2016-03-26 2:10 ` John Cowan
2016-03-26 3:09 ` Charles Anthony
2016-03-26 19:43 ` Clem Cole
2016-03-26 20:54 ` Ronald Natalie [this message]
2016-03-26 22:05 ` John Cowan
2016-03-27 1:25 ` Dave Horsfall
2016-03-27 1:50 ` Charles Anthony
2016-03-27 2:01 ` Greg 'groggy' Lehey
2016-03-27 6:18 ` Random832
2016-03-27 6:57 ` Greg 'groggy' Lehey
2016-03-27 19:38 ` Dave Horsfall
2016-03-27 1:35 ` Greg 'groggy' Lehey
2016-03-26 3:54 ` [TUHS] Is the Teletype the unsung hero of Unix? Greg 'groggy' Lehey
2016-03-26 4:30 ` Steve Nickolas
2016-03-26 5:44 ` Greg 'groggy' Lehey
2016-03-26 8:33 ` Steve Nickolas
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=4B49E73B-51BD-4834-AA8C-5F9F74BA784E@ronnatalie.com \
--to=ron@ronnatalie.com \
/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).