From: steve@quintile.net (Steve Simon)
Subject: [TUHS] SunOS 4 documentation
Date: Thu, 13 Apr 2017 17:34:44 +0100 [thread overview]
Message-ID: <47E9A616-0D37-45DA-841E-70F229045423@quintile.net> (raw)
In-Reply-To: <CAJfiPzwcGNPYkGaMaU6Cav7HkTERE=_MCzZ16pQAPOEjOGEq9w@mail.gmail.com>
i haven't tried it in anger but bwk's pm(1) troff post-proscessor, which does paragraph at at a time layout, is available as a plan9 package. written in c++ so early that cfront will compile it.
-Steve
> On 13 Apr 2017, at 15:14, Nemo <cym224 at gmail.com> wrote:
>
> On 12 April 2017 at 22:20, Larry McVoy <lm at mcvoy.com> wrote:
> [..
>>> While troff can get stuff done in its area, for heavy duty work and exacting
>>> typography, TeX's markup blows troff out of the water, I am afraid.
>>
>> I'd like to learn more about that. I'd done a ton of stuff in troff,
>> had to do a paper recently in LaTex and I did not find it at all better.
>> It was a technical paper, usual stuff, text and tables and figures
>> and references. I'm not great at LaTex so maybe it's just my bias
>> but I really like troff. In fairness, I like groff, I got James to hack
>> some stuff into pic for me.
>>
>> But it started with troff. I still remember walking out of the computer
>> science bookstore with a copy of the troff manual. That was sort of my
>> introduction to Unix and it fits.
>
> I started off with troff (on Suns) and then the dep't installed (La)TeX. I
> switched to LaTeX because I was writing math and it looks better in the
> latter (as Knuth intended). I dabbled with TeX but never stuck to it -- too
> much like assembler. Interestingly, the secretarial staff learnt TeX and
> the grad students all used LaTeX.
>
> At work, we once used noweb (and xfig and pstex) to document our code.
> This was well before doxygen and I think it worked fairly well (despite the
> extra steps).
>
> N.
next prev parent reply other threads:[~2017-04-13 16:34 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 21:54 Cory Smelosky
2017-04-12 22:55 ` Cory Smelosky
2017-04-12 23:31 ` Larry McVoy
2017-04-13 2:13 ` Toby Thain
2017-04-13 2:16 ` Steve Nickolas
2017-04-13 2:25 ` [TUHS] TeX/troff/typesetting markups - " Toby Thain
2017-04-13 14:25 ` Nemo
2017-04-13 15:41 ` Andreas Kusalananda Kähäri
2017-04-13 16:35 ` Toby Thain
2017-04-13 2:20 ` [TUHS] " Larry McVoy
2017-04-13 13:41 ` Steffen Nurpmeso
2017-04-13 15:40 ` [TUHS] TeX/troff/typesetting markups - " Toby Thain
2017-04-13 23:22 ` Steffen Nurpmeso
2017-04-14 0:40 ` Greg 'groggy' Lehey
2017-04-14 1:59 ` Nemo
2017-04-14 3:00 ` Toby Thain
2017-04-14 2:59 ` Toby Thain
2017-04-14 13:38 ` Steffen Nurpmeso
2017-04-14 13:56 ` Michael Kerpan
2017-04-14 16:55 ` Steffen Nurpmeso
2017-04-14 22:24 ` Toby Thain
[not found] ` <CAHfSdrVAnPn3hwFR0ie0o-yuqGX0hu+LWweNZngpoY4=efTSaA@mail.gmail.com>
2017-04-15 14:23 ` Michael Kerpan
2017-04-15 15:09 ` Toby Thain
2017-04-15 16:07 ` [TUHS] TeX/troff/typesetting markups - " Mutiny
2017-04-15 21:48 ` Dave Horsfall
2017-04-15 22:12 ` ron minnich
2017-04-16 0:02 ` Dave Horsfall
2017-04-15 15:27 ` [TUHS] TeX/troff/typesetting markups - " Clem Cole
2017-04-15 17:05 ` Toby Thain
2017-04-15 17:10 ` Toby Thain
2017-04-18 4:49 ` Greg 'groggy' Lehey
2017-04-14 13:07 ` Wolfgang Helbig
2017-04-14 20:56 ` Clem Cole
2017-04-16 13:42 ` Tim Bradshaw
2017-04-13 14:14 ` [TUHS] " Nemo
2017-04-13 16:34 ` Steve Simon [this message]
2017-04-13 23:14 ` Steffen Nurpmeso
2017-04-14 8:30 ` Steve Simon
2017-04-14 13:21 ` Steffen Nurpmeso
2017-04-13 13:28 ` John Labovitz
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=47E9A616-0D37-45DA-841E-70F229045423@quintile.net \
--to=steve@quintile.net \
/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).