From: ron@ronnatalie.com (Ronald Natalie)
Subject: [TUHS] [Groff] It is time to modernise "groff"
Date: Wed, 6 Sep 2017 17:09:26 -0400 [thread overview]
Message-ID: <1951558B-CEB4-4FA8-B1C3-AF4C4CC5A4E2@ronnatalie.com> (raw)
In-Reply-To: <8d29b01ec8813a2fdb56db781095043db1673bc2@webmail.yaccman.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 756 bytes --]
> On Sep 5, 2017, at 11:06 PM, Steve Johnson <scj at yaccman.com> wrote:
>
> One day, I was attempting to print out a one-page document. I ran troff piped into the phototypesetter and got out my roll of paper and fed it into the developer. Out the other end came a page with only one line on it (beautifully typeset): "cannot open input file xxx" A number of others had similar experiences, and stderr was born…
I hear you. Postscript lacked the concept as well. I remember spending bucks on a phototypesetter run just to find an error message as the only thing on print run.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170906/d22562b7/attachment.html>
next prev parent reply other threads:[~2017-09-06 21:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 15:45 Doug McIlroy
2017-09-04 18:28 ` Jon Steinhart
2017-09-04 20:25 ` ron minnich
2017-09-05 16:31 ` Dan Cross
2017-09-05 17:55 ` Nemo
2017-09-06 3:06 ` Steve Johnson
2017-09-06 3:35 ` Jon Steinhart
2017-09-06 21:09 ` Ronald Natalie [this message]
2017-09-04 20:43 ` Lyndon Nerenberg
2017-09-04 21:53 ` Steffen Nurpmeso
2017-09-04 18:28 ` Nemo
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=1951558B-CEB4-4FA8-B1C3-AF4C4CC5A4E2@ronnatalie.com \
--to=ron@ronnatalie.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).