From: Hellwig Geisse <hellwig.geisse@mni.thm.de>
To: KenUnix <ken.unix.guy@gmail.com>, UNIX TUHS Group <tuhs@tuhs.org>
Subject: [TUHS] Re: 'more' command for Unix V7
Date: Thu, 16 Feb 2023 16:06:15 +0100 [thread overview]
Message-ID: <1676559975.2425.172.camel@mni.thm.de> (raw)
In-Reply-To: <CAJXSPs8MRXmNi93u=fAfJy9-9p7BpZCK=GsnuV6Fqwc=SOKBpg@mail.gmail.com>
On Do, 2023-02-16 at 09:24 -0500, KenUnix wrote:
>
> * - I'm not sure where they hid errno if there was one. I'd think
> * there had to be. Maybe Kernighan or Pike knows...
It's a .comm variable, as you can see, e.g., in
/usr/src/libc/crt/cerror.s in Keith Bostic's V7.
Hellwig
next prev parent reply other threads:[~2023-02-16 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 14:24 [TUHS] " KenUnix
2023-02-16 15:06 ` Hellwig Geisse [this message]
2023-02-16 15:23 ` [TUHS] " KenUnix
2023-02-16 16:20 ` Hellwig Geisse
2023-02-17 0:19 ` KenUnix
2023-02-17 6:55 ` Hellwig Geisse
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=1676559975.2425.172.camel@mni.thm.de \
--to=hellwig.geisse@mni.thm.de \
--cc=ken.unix.guy@gmail.com \
--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).