From: markus schnalke <meillo@marmaro.de>
To: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: ed: f command (facts vs. file)
Date: Fri, 22 Jul 2022 18:17:52 +0200 [thread overview]
Message-ID: <1oEvLc-6uI-00@marmaro.de> (raw)
In-Reply-To: <1oDOM5-6wl-00@marmaro.de>
Hoi.
[2022-07-18 12:52] markus schnalke <meillo@marmaro.de>
> [2022-07-11 19:30] Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
> >
> > Lomutu and Lomuto, "A Unix Primer"
>
> Thanks for the recommendation of this book. I now have a copy and
> am looking forward to reading it.
Now I enjoy reading through the book. Thereby I came across this
piece of information (section 7.3.3, p. 87):
(Historically, f stands for ``facts'', but most people
prefer to think of it as an abbreviation for ``file''.)
Why ``facts''?
The manpage in 1st Edition does not list an f command at all.
The manpage in 3rd Edition explains f as ``the filename command''.
Assember and C sources of various editions all talk about filename
and none about facts.
Neither does ``facts'' seem to come from qed.
I couldn't find an f command there at all.
https://www.multicians.org/mspm/bx-9-06.681115.qed-editor.pdf
http://www.bitsavers.org/pdf/honeywell/multics/swenson/6906.multics-condensed-guide.pdf
What's the background for the comment about ``facts''?
meillo
next prev parent reply other threads:[~2022-07-22 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 17:30 [TUHS] Re: ed: multiple addresses (with semicolons) Douglas McIlroy
2022-07-18 10:52 ` markus schnalke
2022-07-22 16:17 ` markus schnalke [this message]
2022-07-22 17:14 ` [TUHS] Re: ed: f command (facts vs. file) Phil Budne
2022-07-23 5:47 ` markus schnalke
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=1oEvLc-6uI-00@marmaro.de \
--to=meillo@marmaro.de \
--cc=tuhs@tuhs.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).