The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] It is time to modernise "groff"
Date: Tue, 5 Sep 2017 07:14:34 -0700	[thread overview]
Message-ID: <20170905141434.GL14353@mcvoy.com> (raw)
In-Reply-To: <201709051137.v85BbGTU005695@coolidge.cs.Dartmouth.EDU>

On Tue, Sep 05, 2017 at 07:37:16AM -0400, Doug McIlroy wrote:
> > > p) Remove the '-a' option (the ASCII approximation output).
> > 
> > I didn't even know this existed.  Looking at what it spits out, I find
> > myself wondering what good it is.  Is this for Unix troff compatibility?
> > For people who didn't even have glass TTYs and needed to imagine what
> > the typeset output would look like?
> 
> Here's a classic use:
> 
> Since groff is not WYSIWYG, the experimental cycle is long:
> edit - save - groff - view. In many cases that cycle can be
> short-circuited by typing straight into groff -a.

If that is the one that makes pic try to do stuff in ascii I've used
that a lot in the days of yore.

I've found, maybe it's no longer true, but back when I was at Sun 25
years ago, that I got farther with execs if I formatted my stuff two
ways: as postscript (or PDF today) and as ascii.  I would send the
ascii version with a header that said "Read this, this is what I 
was babbling about, there is a printable version attached".

It was crazy but my influence with the execs went way up and I came
to the conclusion they didn't read attachments.

That's probably all changed, everyone has a mailer that formats
html and people send their stuff that way.

But there's another use for -a.


      parent reply	other threads:[~2017-09-05 14:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05 11:37 Doug McIlroy
2017-09-05 13:27 ` Steve Simon
2017-09-05 14:40   ` Larry McVoy
2017-09-05 14:14 ` Larry McVoy [this message]

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=20170905141434.GL14353@mcvoy.com \
    --to=lm@mcvoy.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).