The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
* Re: [TUHS] Brian Kernighan and very early *roff history
@ 2022-01-14 13:07 Noel Chiappa
  2022-01-14 13:27 ` Angelo Papenhoff
  0 siblings, 1 reply; 13+ messages in thread
From: Noel Chiappa @ 2022-01-14 13:07 UTC (permalink / raw)
  To: tuhs; +Cc: jnc

    > From: Angelo Papenhoff

    > to my knowledge no troff version before the C rewrite in v7

Apologies if I missed something, but between this list and COFF there's so
much low S/N traffic I skip a lot of it. Having said that, was there ever a
troff in assembler? I'd always had the impression that the first one was in C.

    > The v6 distribution has deleted directory entries for troff source but
    > not the files themselves.  I hope it is not lost. Maybe someone here has
    > an idea where it could be found?

The MIT 'V6+' (I think it's probably basically PWB1) system had troff -
i guess it 'fell off the back of a truck', like a lot of other stuff MIT had,
such as 'typesetter C', the Portable C Compiler, etc.

Theirs was modified to produce output for a Varian (I forget which model,
maybe the docs or driver say).

nroff on that system seems to have been generated from the troff sources; the
assembler nroff sources aren't present.

I looked at its n1.c, and compared it to the V7 one:

  https://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/src/cmd/troff/n1.c

and this one appears to be slightly earlier; e.g. it starts:

  #include "tdef.h"
  #include "t.h"
  #include "tw.h"
  /*
  troff1.c

  consume options, initialization, main loop,
  input routines, escape function calling
  */

  extern int stdi;

and in the argument processing, it has quite a lot fewer.

So that one is a "troff version before the C rewrite in .. v7", but it is in
C. Is that of any interest?

	Noel

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [TUHS] Brian Kernighan and very early *roff history
  2022-01-14 13:07 [TUHS] Brian Kernighan and very early *roff history Noel Chiappa
@ 2022-01-14 13:27 ` Angelo Papenhoff
  2022-01-14 13:35   ` Ralph Corderoy
  2022-01-14 14:25   ` Will Senn
  0 siblings, 2 replies; 13+ messages in thread
From: Angelo Papenhoff @ 2022-01-14 13:27 UTC (permalink / raw)
  To: tuhs

On 14/01/22, Noel Chiappa wrote:
>     > From: Angelo Papenhoff
> 
>     > to my knowledge no troff version before the C rewrite in v7
> 
> Apologies if I missed something, but between this list and COFF there's so
> much low S/N traffic I skip a lot of it. Having said that, was there ever a
> troff in assembler? I'd always had the impression that the first one was in C.

Yes, they were both originally written in assembler. v6 has assembler
sources for nroff and deleted directory entries of troff (and others):

00064e00: 6d01 726f 6666 332e 7300 0000 0000 0000  m.roff3.s.......
00064e10: 6c01 726f 6666 342e 7300 0000 0000 0000  l.roff4.s.......
00064e20: 6b01 726f 6666 352e 7300 0000 0000 0000  k.roff5.s.......
00064e30: 6a01 726f 6666 372e 7300 0000 0000 0000  j.roff7.s.......
00064e40: 6901 726f 6666 382e 7300 0000 0000 0000  i.roff8.s.......
00064e50: 0000 7375 6672 6300 0000 0000 0000 0000  ..sufrc.........
00064e60: 6701 7375 6674 6162 2e73 0000 0000 0000  g.suftab.s......
00064e70: 0000 7463 6174 7369 6d2e 7300 0000 0000  ..tcatsim.s.....
00064e80: 0000 7472 6300 0000 0000 0000 0000 0000  ..trc...........
00064e90: 0000 7472 6f66 6631 2e73 0000 0000 0000  ..troff1.s......
00064ea0: 0000 7472 6f66 6632 2e73 0000 0000 0000  ..troff2.s......
00064eb0: 0000 7472 6f66 6633 2e73 0000 0000 0000  ..troff3.s......
00064ec0: 0000 7472 6f66 6634 2e73 0000 0000 0000  ..troff4.s......
00064ed0: 0000 7472 6f66 6635 2e73 0000 0000 0000  ..troff5.s......
00064ee0: 0000 7472 6f66 6636 2e73 0000 0000 0000  ..troff6.s......
00064ef0: 0000 7472 6f66 6636 6100 0000 0000 0000  ..troff6a.......
00064f00: 0000 7472 6f66 6638 2e73 0000 0000 0000  ..troff8.s......
00064f10: 0000 7878 7878 7800 0000 0000 0000 0000  ..xxxxx.........

> So that one is a "troff version before the C rewrite in .. v7", but it is in
> C. Is that of any interest?

Without having looked into it more than you have it looks like it is
just an earlier version of the C code, but what I'm after is the
original assembly.

aap

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [TUHS] Brian Kernighan and very early *roff history
  2022-01-14 13:27 ` Angelo Papenhoff
@ 2022-01-14 13:35   ` Ralph Corderoy
  2022-01-14 13:55     ` Will Senn
  2022-01-14 14:25   ` Will Senn
  1 sibling, 1 reply; 13+ messages in thread
From: Ralph Corderoy @ 2022-01-14 13:35 UTC (permalink / raw)
  To: tuhs

Hi aap,

> v6 has assembler sources for nroff and deleted directory entries of
> troff (and others):
>
> 00064e00: 6d01 726f 6666 332e 7300 0000 0000 0000  m.roff3.s.......
> 00064e10: 6c01 726f 6666 342e 7300 0000 0000 0000  l.roff4.s.......
> 00064e20: 6b01 726f 6666 352e 7300 0000 0000 0000  k.roff5.s.......
> 00064e30: 6a01 726f 6666 372e 7300 0000 0000 0000  j.roff7.s.......
> 00064e40: 6901 726f 6666 382e 7300 0000 0000 0000  i.roff8.s.......
> 00064e50: 0000 7375 6672 6300 0000 0000 0000 0000  ..sufrc.........
> 00064e60: 6701 7375 6674 6162 2e73 0000 0000 0000  g.suftab.s......
> 00064e70: 0000 7463 6174 7369 6d2e 7300 0000 0000  ..tcatsim.s.....
> 00064e80: 0000 7472 6300 0000 0000 0000 0000 0000  ..trc...........
> 00064e90: 0000 7472 6f66 6631 2e73 0000 0000 0000  ..troff1.s......

Are inodes 0x0168, etc., re-used elsewhere?  If so, it would be
interesting to where.

Or is there a chance they still hold useful information about blocks
which may contain troff content?

-- 
Cheers, Ralph.

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [TUHS] Brian Kernighan and very early *roff history
  2022-01-14 13:35   ` Ralph Corderoy
@ 2022-01-14 13:55     ` Will Senn
  2022-01-14 13:58       ` Will Senn
  0 siblings, 1 reply; 13+ messages in thread
From: Will Senn @ 2022-01-14 13:55 UTC (permalink / raw)
  To: Ralph Corderoy, tuhs

Hi AAP,

Dunno if this is what you're after, but Dennis's v5 tape has roff 
assembly sources in s7 
https://www.tuhs.org/Archive/Distributions/Research/Dennis_v5/v5root.tar.gz:


Will

On 1/14/22 7:35 AM, Ralph Corderoy wrote:
> Hi aap,
>
>> v6 has assembler sources for nroff and deleted directory entries of
>> troff (and others):
>>
>> 00064e00: 6d01 726f 6666 332e 7300 0000 0000 0000  m.roff3.s.......
>> 00064e10: 6c01 726f 6666 342e 7300 0000 0000 0000  l.roff4.s.......
>> 00064e20: 6b01 726f 6666 352e 7300 0000 0000 0000  k.roff5.s.......
>> 00064e30: 6a01 726f 6666 372e 7300 0000 0000 0000  j.roff7.s.......
>> 00064e40: 6901 726f 6666 382e 7300 0000 0000 0000  i.roff8.s.......
>> 00064e50: 0000 7375 6672 6300 0000 0000 0000 0000  ..sufrc.........
>> 00064e60: 6701 7375 6674 6162 2e73 0000 0000 0000  g.suftab.s......
>> 00064e70: 0000 7463 6174 7369 6d2e 7300 0000 0000  ..tcatsim.s.....
>> 00064e80: 0000 7472 6300 0000 0000 0000 0000 0000  ..trc...........
>> 00064e90: 0000 7472 6f66 6631 2e73 0000 0000 0000  ..troff1.s......
> Are inodes 0x0168, etc., re-used elsewhere?  If so, it would be
> interesting to where.
>
> Or is there a chance they still hold useful information about blocks
> which may contain troff content?
>


^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [TUHS] Brian Kernighan and very early *roff history
  2022-01-14 13:55     ` Will Senn
@ 2022-01-14 13:58       ` Will Senn
  0 siblings, 0 replies; 13+ messages in thread
From: Will Senn @ 2022-01-14 13:58 UTC (permalink / raw)
  To: Ralph Corderoy, tuhs

On 1/14/22 7:55 AM, Will Senn wrote:
> Hi AAP,
>
> Dunno if this is what you're after, but Dennis's v5 tape has roff 
> assembly sources in s7 
> https://www.tuhs.org/Archive/Distributions/Research/Dennis_v5/v5root.tar.gz:
>
>
> Will

Oops. You're looking for troff, not roff. Sorry.

Will

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [TUHS] Brian Kernighan and very early *roff history
  2022-01-14 13:27 ` Angelo Papenhoff
  2022-01-14 13:35   ` Ralph Corderoy
@ 2022-01-14 14:25   ` Will Senn
  1 sibling, 0 replies; 13+ messages in thread
From: Will Senn @ 2022-01-14 14:25 UTC (permalink / raw)
  To: Angelo Papenhoff, tuhs

[-- Attachment #1: Type: text/plain, Size: 2950 bytes --]

On 1/14/22 7:27 AM, Angelo Papenhoff wrote:
> On 14/01/22, Noel Chiappa wrote:
>>      > From: Angelo Papenhoff
>>
>>      > to my knowledge no troff version before the C rewrite in v7
>>
>> Apologies if I missed something, but between this list and COFF there's so
>> much low S/N traffic I skip a lot of it. Having said that, was there ever a
>> troff in assembler? I'd always had the impression that the first one was in C.
> Yes, they were both originally written in assembler. v6 has assembler
> sources for nroff and deleted directory entries of troff (and others):
>
> 00064e00: 6d01 726f 6666 332e 7300 0000 0000 0000  m.roff3.s.......
> 00064e10: 6c01 726f 6666 342e 7300 0000 0000 0000  l.roff4.s.......
> 00064e20: 6b01 726f 6666 352e 7300 0000 0000 0000  k.roff5.s.......
> 00064e30: 6a01 726f 6666 372e 7300 0000 0000 0000  j.roff7.s.......
> 00064e40: 6901 726f 6666 382e 7300 0000 0000 0000  i.roff8.s.......
> 00064e50: 0000 7375 6672 6300 0000 0000 0000 0000  ..sufrc.........
> 00064e60: 6701 7375 6674 6162 2e73 0000 0000 0000  g.suftab.s......
> 00064e70: 0000 7463 6174 7369 6d2e 7300 0000 0000  ..tcatsim.s.....
> 00064e80: 0000 7472 6300 0000 0000 0000 0000 0000  ..trc...........
> 00064e90: 0000 7472 6f66 6631 2e73 0000 0000 0000  ..troff1.s......
> 00064ea0: 0000 7472 6f66 6632 2e73 0000 0000 0000  ..troff2.s......
> 00064eb0: 0000 7472 6f66 6633 2e73 0000 0000 0000  ..troff3.s......
> 00064ec0: 0000 7472 6f66 6634 2e73 0000 0000 0000  ..troff4.s......
> 00064ed0: 0000 7472 6f66 6635 2e73 0000 0000 0000  ..troff5.s......
> 00064ee0: 0000 7472 6f66 6636 2e73 0000 0000 0000  ..troff6.s......
> 00064ef0: 0000 7472 6f66 6636 6100 0000 0000 0000  ..troff6a.......
> 00064f00: 0000 7472 6f66 6638 2e73 0000 0000 0000  ..troff8.s......
> 00064f10: 0000 7878 7878 7800 0000 0000 0000 0000  ..xxxxx.........
>
>> So that one is a "troff version before the C rewrite in .. v7", but it is in
>> C. Is that of any interest?
> Without having looked into it more than you have it looks like it is
> just an earlier version of the C code, but what I'm after is the
> original assembly.
>
> aap
I don't really know how deeply you've looked into this, but it may be of 
interest to you that Wollongong v6 on Interdata 32 has C sources for 
troff in /usr/source/troff:
http://www.bitsavers.org/bits/Interdata/32bit/unix/univWollongong_v6/interdata_v6.tar.gz

I know you're looking for assembler, but I also saw the comment "C 
rewrite in .. v7" in the message. It looks like a C version was 
available for v6. According to Miller's note:

interdata_v6.tar.gz
   a 'tar' format archive (with dates preserved) of all files as
   they would appear after installing the distribution, with source
   and documentation in /usr/source and /usr/doc respectively; note
   however that special files in /dev appear as ordinary files

The troff dir has date Jun 6, 1978. According to the readme, it was 
untested (maybe even unported?).

Will


[-- Attachment #2: Type: text/html, Size: 3859 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [TUHS] Brian Kernighan and very early *roff history
  2022-01-14 10:13   ` Jaap Akkerhuis
  2022-01-14 11:48     ` Rob Pike
@ 2022-01-14 14:08     ` Larry McVoy
  1 sibling, 0 replies; 13+ messages in thread
From: Larry McVoy @ 2022-01-14 14:08 UTC (permalink / raw)
  To: Jaap Akkerhuis; +Cc: The Eunuchs Hysterical Society

On Fri, Jan 14, 2022 at 11:13:35AM +0100, Jaap Akkerhuis wrote:
> 
> 
> > On Jan 14, 2022, at 1:10, Rob Pike <robpike@gmail.com> wrote:
> > 
> > Dennis spent quite a bit of time cleaning up the troff code in the late 1980s, if I remember right, moving it to modern C. He got annoyed by it one day.
> 
> If I remember correctly, it was actually Ken.  He also turned it
> in a single binary.  (Troff -N turned it into nroff).
> 
> > It was the "ditroff" variant although honestly I don't remember us ever calling it that. It was just the current version of troff. Not sure where the name came from. Perhaps it was us but I think of it as a foreign name.
> 
> Originally Brian called it "Typesetter Independent Troff" in the
> article he wrote about it and for some reason people started to
> call it "Device Independent".

TIT vs DIT might be why?

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [TUHS] Brian Kernighan and very early *roff history
  2022-01-14  0:04 Tom Lyon via TUHS
  2022-01-14  0:10 ` Rob Pike
@ 2022-01-14 11:59 ` Angelo Papenhoff
  1 sibling, 0 replies; 13+ messages in thread
From: Angelo Papenhoff @ 2022-01-14 11:59 UTC (permalink / raw)
  To: The Eunuchs Hysterical Society

Since the topic is on the history of troff, I'd like to mention again
that to my knowledge no troff version before the C rewrite in v7
is publicly available anywhere. v6 only has nroff, v5 only has roff
even though nroff/troff appeared in v4.
The v6 distribution has deleted directory entries for troff source
but not the files themselves.
I hope it is not lost. Maybe someone here has an idea where it could be
found?

aap

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [TUHS] Brian Kernighan and very early *roff history
  2022-01-14 10:13   ` Jaap Akkerhuis
@ 2022-01-14 11:48     ` Rob Pike
  2022-01-14 14:08     ` Larry McVoy
  1 sibling, 0 replies; 13+ messages in thread
From: Rob Pike @ 2022-01-14 11:48 UTC (permalink / raw)
  To: Jaap Akkerhuis; +Cc: The Eunuchs Hysterical Society

[-- Attachment #1: Type: text/plain, Size: 937 bytes --]

It was definitely Dennis, at least for the cleanup part I was referring to.

-rob


On Fri, Jan 14, 2022 at 9:14 PM Jaap Akkerhuis <jaapna@xs4all.nl> wrote:

>
>
> > On Jan 14, 2022, at 1:10, Rob Pike <robpike@gmail.com> wrote:
> >
> > Dennis spent quite a bit of time cleaning up the troff code in the late
> 1980s, if I remember right, moving it to modern C. He got annoyed by it one
> day.
>
> If I remember correctly, it was actually Ken.  He also turned it
> in a single binary.  (Troff -N turned it into nroff).
>
> > It was the "ditroff" variant although honestly I don't remember us ever
> calling it that. It was just the current version of troff. Not sure where
> the name came from. Perhaps it was us but I think of it as a foreign name.
>
> Originally Brian called it "Typesetter Independent Troff" in the
> article he wrote about it and for some reason people started to
> call it "Device Independent".
>
>         jaap
>
>

[-- Attachment #2: Type: text/html, Size: 1413 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [TUHS] Brian Kernighan and very early *roff history
  2022-01-14  0:10 ` Rob Pike
  2022-01-14  7:38   ` arnold
@ 2022-01-14 10:13   ` Jaap Akkerhuis
  2022-01-14 11:48     ` Rob Pike
  2022-01-14 14:08     ` Larry McVoy
  1 sibling, 2 replies; 13+ messages in thread
From: Jaap Akkerhuis @ 2022-01-14 10:13 UTC (permalink / raw)
  To: Rob Pike; +Cc: The Eunuchs Hysterical Society

[-- Attachment #1: Type: text/plain, Size: 753 bytes --]



> On Jan 14, 2022, at 1:10, Rob Pike <robpike@gmail.com> wrote:
> 
> Dennis spent quite a bit of time cleaning up the troff code in the late 1980s, if I remember right, moving it to modern C. He got annoyed by it one day.

If I remember correctly, it was actually Ken.  He also turned it
in a single binary.  (Troff -N turned it into nroff).

> It was the "ditroff" variant although honestly I don't remember us ever calling it that. It was just the current version of troff. Not sure where the name came from. Perhaps it was us but I think of it as a foreign name.

Originally Brian called it "Typesetter Independent Troff" in the
article he wrote about it and for some reason people started to
call it "Device Independent".

	jaap


[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 267 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [TUHS] Brian Kernighan and very early *roff history
  2022-01-14  0:10 ` Rob Pike
@ 2022-01-14  7:38   ` arnold
  2022-01-14 10:13   ` Jaap Akkerhuis
  1 sibling, 0 replies; 13+ messages in thread
From: arnold @ 2022-01-14  7:38 UTC (permalink / raw)
  To: robpike, pugs; +Cc: tuhs

The name 'ditroff' for Device Independent Troff was how AT&T marketed /
sold / licensed it when they released it to the world.  The new name
was necessary to distinguish it from the original troff in V7 / System III /
System V.

It's understandable that inside Research no such distinction was made.
Nonetheless, the V8 and V10 archives show that the C/A/T variant was
still around (at least in /usr/src/cmd) under the name otroff.

HTH,

Arnold

Rob Pike <robpike@gmail.com> wrote:

> Dennis spent quite a bit of time cleaning up the troff code in the late
> 1980s, if I remember right, moving it to modern C. He got annoyed by it one
> day. It was the "ditroff" variant although honestly I don't remember us
> ever calling it that. It was just the current version of troff. Not sure
> where the name came from. Perhaps it was us but I think of it as a foreign
> name.
>
> -rob
>
>
> On Fri, Jan 14, 2022 at 11:05 AM Tom Lyon via TUHS <tuhs@minnie.tuhs.org>
> wrote:
>
> > Most of y'all are aware of Brian Kernighan's troff involvement. My
> > understanding is that he pretty much took over nroff/troff after Joe Ossana
> > died, and came out with ditroff.
> >
> > But Brian had much earlier involvement with non-UNIX *roff.  When he was
> > pursuing his PhD at Princeton, he spent a summer at MIT using CTSS and
> > RUNOFF.  When he came back to P'ton, he wrote a ROFF for the IBM 7094,
> > later translated to the IBM 360.  Many generations of students, myself
> > included, use the IBM ROFF (batch, not interactive) as a much friendlier
> > alternative to dumb typewriters.  I don't know if 360 ROFF spread beyond
> > Princeton, but I wouldn't be surprised.
> >
> > BTW, during my summer at Bell, nroff/troff was one of the few programs I
> > could not port to the Interdata 8/32 - it was just a mess of essentially
> > typeless code.  I don't think Joe Ossana got around to it either before he
> > died.
> >
> > --
> > - Tom
> >

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [TUHS] Brian Kernighan and very early *roff history
  2022-01-14  0:04 Tom Lyon via TUHS
@ 2022-01-14  0:10 ` Rob Pike
  2022-01-14  7:38   ` arnold
  2022-01-14 10:13   ` Jaap Akkerhuis
  2022-01-14 11:59 ` Angelo Papenhoff
  1 sibling, 2 replies; 13+ messages in thread
From: Rob Pike @ 2022-01-14  0:10 UTC (permalink / raw)
  To: Tom Lyon; +Cc: The Eunuchs Hysterical Society

[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]

Dennis spent quite a bit of time cleaning up the troff code in the late
1980s, if I remember right, moving it to modern C. He got annoyed by it one
day. It was the "ditroff" variant although honestly I don't remember us
ever calling it that. It was just the current version of troff. Not sure
where the name came from. Perhaps it was us but I think of it as a foreign
name.

-rob


On Fri, Jan 14, 2022 at 11:05 AM Tom Lyon via TUHS <tuhs@minnie.tuhs.org>
wrote:

> Most of y'all are aware of Brian Kernighan's troff involvement. My
> understanding is that he pretty much took over nroff/troff after Joe Ossana
> died, and came out with ditroff.
>
> But Brian had much earlier involvement with non-UNIX *roff.  When he was
> pursuing his PhD at Princeton, he spent a summer at MIT using CTSS and
> RUNOFF.  When he came back to P'ton, he wrote a ROFF for the IBM 7094,
> later translated to the IBM 360.  Many generations of students, myself
> included, use the IBM ROFF (batch, not interactive) as a much friendlier
> alternative to dumb typewriters.  I don't know if 360 ROFF spread beyond
> Princeton, but I wouldn't be surprised.
>
> BTW, during my summer at Bell, nroff/troff was one of the few programs I
> could not port to the Interdata 8/32 - it was just a mess of essentially
> typeless code.  I don't think Joe Ossana got around to it either before he
> died.
>
> --
> - Tom
>

[-- Attachment #2: Type: text/html, Size: 2084 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [TUHS] Brian Kernighan and very early *roff history
@ 2022-01-14  0:04 Tom Lyon via TUHS
  2022-01-14  0:10 ` Rob Pike
  2022-01-14 11:59 ` Angelo Papenhoff
  0 siblings, 2 replies; 13+ messages in thread
From: Tom Lyon via TUHS @ 2022-01-14  0:04 UTC (permalink / raw)
  To: The Eunuchs Hysterical Society

[-- Attachment #1: Type: text/plain, Size: 888 bytes --]

Most of y'all are aware of Brian Kernighan's troff involvement. My
understanding is that he pretty much took over nroff/troff after Joe Ossana
died, and came out with ditroff.

But Brian had much earlier involvement with non-UNIX *roff.  When he was
pursuing his PhD at Princeton, he spent a summer at MIT using CTSS and
RUNOFF.  When he came back to P'ton, he wrote a ROFF for the IBM 7094,
later translated to the IBM 360.  Many generations of students, myself
included, use the IBM ROFF (batch, not interactive) as a much friendlier
alternative to dumb typewriters.  I don't know if 360 ROFF spread beyond
Princeton, but I wouldn't be surprised.

BTW, during my summer at Bell, nroff/troff was one of the few programs I
could not port to the Interdata 8/32 - it was just a mess of essentially
typeless code.  I don't think Joe Ossana got around to it either before he
died.

-- 
- Tom

[-- Attachment #2: Type: text/html, Size: 1345 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

end of thread, other threads:[~2022-01-14 14:26 UTC | newest]

Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-14 13:07 [TUHS] Brian Kernighan and very early *roff history Noel Chiappa
2022-01-14 13:27 ` Angelo Papenhoff
2022-01-14 13:35   ` Ralph Corderoy
2022-01-14 13:55     ` Will Senn
2022-01-14 13:58       ` Will Senn
2022-01-14 14:25   ` Will Senn
  -- strict thread matches above, loose matches on Subject: below --
2022-01-14  0:04 Tom Lyon via TUHS
2022-01-14  0:10 ` Rob Pike
2022-01-14  7:38   ` arnold
2022-01-14 10:13   ` Jaap Akkerhuis
2022-01-14 11:48     ` Rob Pike
2022-01-14 14:08     ` Larry McVoy
2022-01-14 11:59 ` Angelo Papenhoff

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).