The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] TeX/troff/typesetting markups - Re: SunOS 4 documentation
Date: Tue, 18 Apr 2017 14:49:48 +1000	[thread overview]
Message-ID: <20170418044948.GB45593@eureka.lemis.com> (raw)
In-Reply-To: <CAC20D2OR5reLm-BD4Ff+9G_vy=O_b=sSSGZ0q-70qNVFCF_7gg@mail.gmail.com>

On Saturday, 15 April 2017 at 11:27:49 -0400, Clem Cole wrote:
>
> If you grew up with an affinity for one, you are more likely to find
> it more comfortable for your needs.  I find a TeX just as ugly and
> unreadable as the runoff family with troff is a member.

FWIW, I grew up with TeX, but when I wrote "Porting UNIX Software" for
O'Reilly, they wanted the markup in groff with their adaptation of the
mm macro set.  I was game, and it worked well.  And then I discovered
I didn't want to go back to TeX.  I stuck with groff, and 20 years
later I'm still using it.


  parent reply	other threads:[~2017-04-18  4:49 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12 21:54 [TUHS] " 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 [this message]
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
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
2017-04-17 18:56 [TUHS] TeX/troff/typesetting markups - " Doug McIlroy

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=20170418044948.GB45593@eureka.lemis.com \
    --to=grog@lemis.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).