🚀 go-pugleaf

In my original query I discussed the need to clone environments (in groff),
and asked for ideas and thoughts on the subject.

I got two answers, one of which was posted to then net. In his response
Mark Bergman (bergman@panix.com) recommended me to source (.so) the 
definitions of a particular environment whenever I need it. This doesn't 
quite do what I want, unfortunately.

The great guru and *roff-wizard James Clark (jjc@clark.com) advised me to
stick to the method of pushing and popping on/off a variable stack (the
way it's done in -mgm).

Environments contain ``unnecessary'' information that possibly could 
mess up my text if I clone and pop environments at will. Environments are
apparently best for non-text-flow processing such as headers and footers.

The environment constructor I mentioned wouldn't do what I wanted, anyway.
It's for creating temporary environments for \w etc. processing.

I guess I'll follow the advice James gave me.

Sverre

--------------------------------------------------------------------------
Sverre Slotte Jr.                      Internet:  sverre@research.nokia.fi
Nokia Research Center                  Phone:              + 358 0 4376208
P.O.Box 156, 02101 Esbo, FINLAND       Phax:               + 358 0 4376227
X.400 mail:        G=sverre; S=slotte; O=research; P=nokia; A=fumail; C=fi
--------------------------------------------------------------------------

Wer nich liebt Wein, Weib und Gesang, der bleibt ein Narr sein Leben lang.
                                                             Martin Luther