From: Clem Cole <clemc@ccc.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: Computer Old Farts Followers <coff@tuhs.org>
Subject: Re: [COFF] Scribe (Typesetting System) and Unix
Date: Thu, 13 Jan 2022 11:54:51 -0500 [thread overview]
Message-ID: <CAC20D2Os2YaOKeF7HGoOfVvv7QnLEsc+w_YuUK32JURCTqnSaw@mail.gmail.com> (raw)
In-Reply-To: <20220113165207.GD7175@mcvoy.com>
[-- Attachment #1.1: Type: text/plain, Size: 1478 bytes --]
On Thu, Jan 13, 2022 at 11:52 AM Larry McVoy <lm@mcvoy.com> wrote:
> On Thu, Jan 13, 2022 at 04:42:53PM +0000, Lars Brinkhoff wrote:
> > Clem Cole wrote:
> > > I always got the impression that texinfo was more of a shot against
> > > man pages and trying to push the purity of the 'ITS-way' to Unix.
> >
> > ITS had a hypertext documentation system, so my assumtion would be that
> > RMS wanted to bring along that to the GNU vision. I don't see that's it
> > would be abount purity, whatever that would mean for documentation.
>
> So you know how when you go into someone else's program to fix a bug and
> they have a hideous coding style? Have you ever had someone else fix a
> bug in your code and they reformat everything so git blame looks like
> they wrote the whole thing? That's rude, right? If you were fixing
> the bug in some crappy coding style, you fix it in that crappy coding
> style, it's not your style but it is the polite thing to do.
>
> If we agree on that then we can move on to RMS and texinfo. Providing
> texinfo docs for Unix commands is like reformatting the code. It's
> rude. The Unix way is man pages for basic usage and a user guide,
> usually in -ms. Not doing it that way is trying to change the way
> the system works and it's just rude.
>
> If I were working on ITS and techinfo is how they do their docs, that's
> how I'd do docs there, it would be rude to force man pages on system
> that doesn't work that way.
>
Amen bro ... Amen
[-- Attachment #1.2: Type: text/html, Size: 2170 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
next prev parent reply other threads:[~2022-01-13 16:55 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
2022-01-13 16:42 ` Lars Brinkhoff
2022-01-13 16:52 ` Larry McVoy
2022-01-13 16:54 ` Clem Cole [this message]
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=CAC20D2Os2YaOKeF7HGoOfVvv7QnLEsc+w_YuUK32JURCTqnSaw@mail.gmail.com \
--to=clemc@ccc.com \
--cc=coff@tuhs.org \
--cc=lm@mcvoy.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).