9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] troff and ps related
Date: Wed,  8 Jul 2009 08:29:05 -0700	[thread overview]
Message-ID: <dd6fe68a0907080829u4daf2d05m9f777776dfe69c33@mail.gmail.com> (raw)
In-Reply-To: <a560a5d00907080803t192db66dkdbad6b070f4e5d99@mail.gmail.com>

I assume you have a non-Plan 9 machine to play with.
It's worth trying Heirloom troff there to see if the boxes
are done better.  They probably are.  It would be a big
integration effort to fit the Heirloom troff changes into the
Plan 9 troff changes.  Maybe it is worth it; maybe not.

I like Heirloom troff for papers for its better handling of
postscript and opentype fonts, although when I need
to do nasty low-level things (like I do to generate slides)
I need to fall back to the Plan 9 troff, because the low-level
details seem to differ between the two.

Honestly the box drawing has never really bothered me.
I don't draw boxes around things because it's too noisy
for my tastes anyway.  Faulting troff for its box drawing is
like faulting a web browser for its text blinking.

> Do you think that troff is really dead?

Is my pocketknife dead?  Was it ever alive?
When troff does what I need it to do and is the quickest
way for me to get that done, it's the right tool for me.
It may not be the right tool for you.

Russ

P.S. For what it's worth, the Plan 9 troff reads tex
hyphenation rules too.


  reply	other threads:[~2009-07-08 15:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08 11:49 Rudolf Sykora
2009-07-08 12:13 ` erik quanstrom
2009-07-08 14:27 ` Russ Cox
2009-07-08 15:03   ` Rudolf Sykora
2009-07-08 15:29     ` Russ Cox [this message]
2009-07-09 14:53       ` Rudolf Sykora
2009-07-09 16:54         ` hiro
2009-07-09 17:59           ` yy
2009-07-08 16:08     ` Dan Cross

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=dd6fe68a0907080829u4daf2d05m9f777776dfe69c33@mail.gmail.com \
    --to=rsc@swtch.com \
    --cc=9fans@9fans.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).