groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Groff] Line continuation


From: Clarke Echols
Subject: Re: [Groff] Line continuation
Date: Mon, 27 Oct 2008 14:12:36 -0600
User-agent: Thunderbird 2.0.0.17 (X11/20080925)

I looked at the HP site and the manuals are no longer available.
I also checked the other sources that took some of the old HP
stuff for on-demand printing, but they don't have it either.

I have a copy but it's protected by copyright.  If there were enough
demand, I could consider a rewrite, but I don't know that there'd
be enough people willing to part with the cash, given the mentality
of the interenet where everything [should be] free of charge. :-(

Keep in mind, I wrote it 20 years ago...

And the corporate mentality is if it isn't making money hand over
fist, it isn't worth doing.

Clarke

walter harms wrote:
hi Clarke,
in case you sill have connections to HP. it would be nice if you could
convince them to publish that manuals on the internet.

re,
 wh


Clarke Echols schrieb:
I wrote an extensive tutorial on sed back about 1987 or so.  It's part
of HP's HP-UX User Guide series: "Text Editors and Processors".  I don't
know if you can get your hands on it or not.  I based it on the
sed standards-conformance tests that were run before the software could
be shipped, plus other explanatory stuff.

The thing that confuses people about sed is the concept of "pattern
space".  ^ is the start, and $ is the end, but you can have multiple
lines in the space at the same time, with each adjacent pair
separated by a newline (represented as \n in substitutions and
pattern searches).

It's a very powerful program -- especially when run from inside vi
(vim) and vi is run non-interactively from a shell script by
redirecting input from a command file that ends with "ZZ" or ":wq"
on the last line in the file.

I overhauled the entire HP-UX Reference (manpages) in a few minutes
that way.  Took about 3 hours to write and debug the code, but the
job ran in less than 5 minutes on a 30-MHz processor.  It would
be interesting to see how long it would take on a 2-Ghz machine. :-)

I converted all in-line coding to macros; i.e., \fB became .B, etc.
and I completely changed the typography conventions from AT&T to
current industry practice, and got rid of font inconsistencies too.







reply via email to

[Prev in Thread] Current Thread [Next in Thread]