Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Clem Cole <clemc@ccc.com>
Cc: Computer Old Farts Followers <coff@tuhs.org>
Subject: Re: [COFF] Scribe (Typesetting System) and Unix
Date: Thu, 13 Jan 2022 09:32:14 -0700	[thread overview]
Message-ID: <CANCZdfq4ti5h=hsRCV0440tCobxWXZknZXWxmY527aYHiN6WtQ@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2MiFpDiZQmXyNTx43UG_OMHrtSm65Tyqw4M-LM7LZOtyg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1927 bytes --]

On Thu, Jan 13, 2022 at 9:20 AM Clem Cole <clemc@ccc.com> wrote:

> To be fair, its not an unusual behavior.  Folks coming from VMS (or
> windows) try to make Unix look like that.  And what did we do with VMS, we
> added the cshell and Unix tools so people like me could type on it.   I'm
> currently being driven nuts by the simh tool which has a very TOPS/VMS
> style feel.  Everything is help commands. The documents are quite sparse.
> To me the documents/book (or man pages) should primarily ' go to' and if
> you want something like 'help' then create it from the documents.  But I
> can not really complain. It's a wonderful tool and its author comes from
> that heritage not Unix.  The problem I remind him is that he will get silly
> questions from people like me, because we can not find things in his help
> system - its just not how a Unix program tends to work [I want to look in
> the index of the document, and find the section myself].
>

The different worldviews are instructive. c-kermit had a tops-20 cmd
JSYS built into it and all the escape completion just worked. The  help was
quite good, but as with most help systems it was a zoomed in on some
hyperspecific topic. For that it was usually good (across all the TOPS-20
and VMS and that ilk), but sometimes you got things like "/GERBILS
specifies the gerbils to use" without really telling you what a gerbil was
in this context. what you didn't get was how things held together (eg
/HAMSTERS and /GERBILS worked hand in hand to control parameters to the
rodent models used to generate the ecosystem) or some of the higher level
concepts (like what an ecosystem was).

I used to read the raw VMS help files. They were a verbose version of the
Unix manuals in some ways, though less crisp in others. It was helpful to
read it all to understand, but even so some important concepts were
omitted, or discussed elsewhere w/o a proper cross reference.

Warner

[-- Attachment #1.2: Type: text/html, Size: 2455 bytes --]

[-- Attachment #2: Type: text/plain, Size: 141 bytes --]

_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff

  reply	other threads:[~2022-01-13 16:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13  2:04 josh
2022-01-13  2:03 ` Greg 'groggy' Lehey
2022-01-13  3:24 ` Win Treese
2022-01-13 14:56   ` Clem Cole
2022-01-13 15:08     ` John P. Linderman
2022-01-13 16:06       ` Clem Cole
2022-01-13 16:24         ` Warner Losh
2022-01-13 16:39         ` Harald Arnesen
2022-01-13 18:00         ` Bakul Shah
2022-01-13 15:35     ` Dan Cross
2022-01-13 16:02       ` Warner Losh
2022-01-13 16:20         ` Clem Cole
2022-01-13 16:32           ` Warner Losh [this message]
2022-01-13 16:42           ` Lars Brinkhoff
2022-01-13 16:52             ` Larry McVoy
2022-01-13 16:54               ` Clem Cole
2022-01-13 17:06               ` Clem Cole
2022-01-13 18:16         ` Dan Cross
2022-01-13 20:00           ` Larry McVoy
2022-01-13 20:26           ` Chet Ramey
2022-01-13 16:13       ` Charles H Sauer
2022-01-13 22:53     ` David Arnold
2022-01-14  1:53       ` Adam Thornton
2022-01-13  3:26 ` Theodore Ts'o
2022-01-13 16:25   ` Larry McVoy
2022-01-13 16:33   ` Dan Cross
2022-01-13 22:19     ` David Arnold
2022-01-13 13:54 ` Adam Sampson
2022-01-13 16:37   ` Lars Brinkhoff

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='CANCZdfq4ti5h=hsRCV0440tCobxWXZknZXWxmY527aYHiN6WtQ@mail.gmail.com' \
    --to=imp@bsdimp.com \
    --cc=clemc@ccc.com \
    --cc=coff@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).