The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@iitbombay.org>
To: Larry McVoy <lm@mcvoy.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] TeX and groff (was: roff(7))
Date: Mon, 10 Jan 2022 13:12:34 -0800	[thread overview]
Message-ID: <3781D505-E68C-4EB1-8812-50E60BE8019B@iitbombay.org> (raw)

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


On Jan 10, 2022, at 12:33 PM, Larry McVoy <lm@mcvoy.com> wrote:
> TeX looks better but you instantly know it is
> TeX, it has a particular look.

Perhaps you’re thinking of documents using Computer Modern fonts,
typeset using LaTeX’s document classes. Check out the examples here:
 https://tex.stackexchange.com/questions/1319/showcase-of-beautiful-typography-done-in-tex-friends


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

             reply	other threads:[~2022-01-10 21:12 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 21:12 Bakul Shah [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-01-13 17:31 Douglas McIlroy
2022-01-12  2:49 Jon Steinhart
2022-01-12 10:38 ` Ralph Corderoy
2022-01-12 17:53   ` Jon Steinhart
2022-01-12 18:27     ` G. Branden Robinson
2022-01-12 19:02       ` John Cowan
2022-01-11 13:37 Nelson H. F. Beebe
2022-01-10 21:06 Jon Steinhart
2022-01-11 11:06 ` Ralph Corderoy
2022-01-11 14:52   ` John Cowan
2021-12-31 15:47 [TUHS] roff(7) Douglas McIlroy
2021-12-31 23:07 ` George Michaelson
2021-12-31 23:40   ` Larry McVoy
2022-01-01  0:56     ` [TUHS] TeX and groff (was: roff(7)) Greg 'groggy' Lehey
2022-01-01  3:15       ` Larry McVoy
2022-01-10 19:00         ` Blake McBride
2022-01-10 20:21           ` Jon Forrest
2022-01-11 22:48             ` Blake McBride
2022-01-11 23:18               ` Larry McVoy
2022-01-12  1:19                 ` Dave Horsfall
2022-01-12  1:46                 ` Blake McBride
2022-01-12  2:12                 ` Bakul Shah
2022-01-12 15:49                   ` Larry McVoy
2022-01-12 16:22                     ` Adam Thornton
2022-01-12  0:06               ` Jon Steinhart
2022-01-12  1:48                 ` Blake McBride
2022-01-12  0:29               ` Nemo Nusquam
2022-01-12  1:53                 ` Blake McBride
     [not found]               ` <E3CC4B8A-4E88-4339-A4D3-4ED26BA80620@gmail.com>
2022-01-12  0:44                 ` Jon Forrest
2022-01-12  2:00                   ` Blake McBride
2022-01-12  2:10                     ` David Arnold
2022-01-12  2:26                       ` Adam Thornton
2022-01-12 19:54                     ` John Cowan
2022-01-13 10:13                       ` Thomas Paulsen
2022-01-13 20:00                         ` John Cowan
2022-01-10 20:33           ` Larry McVoy
2022-01-10 20:37             ` Richard Salz
2022-01-10 21:04               ` Dan Cross
2022-01-10 21:48                 ` Nemo Nusquam
2022-01-11  2:25                 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-01-11  2:47                   ` Larry McVoy
2022-01-12  1:19             ` Mary Ann Horton
2022-01-12  2:03               ` Blake McBride
2022-01-12  2:10               ` Bakul Shah
2022-01-12  3:44                 ` Dan Cross
2022-01-12 16:48               ` Steffen Nurpmeso
2022-01-10 20:46           ` Steffen Nurpmeso

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=3781D505-E68C-4EB1-8812-50E60BE8019B@iitbombay.org \
    --to=bakul@iitbombay.org \
    --cc=lm@mcvoy.com \
    --cc=tuhs@minnie.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).