Re: [Groff] Weird problem; .ig is not ignored

[Werner LEMBERG]

> What part of the info documentation for .ig are you referring to?

He is referring to groff.texinfo.

> As I read it, it's a way of commenting out a big chunk of the input.
> Surely that should mean that the commented-out section isn't
> interpreted?

It's not that easy.  From the original AT&T troff manual:

  `ig' behaves exactly like `de' except that the input is discarded.
  The input is read in copy mode, and any auto-incremented registers
  will be affected.

> solaris troff : adding the .ig section doesn't change output
> groff 1.18.1.1: same here
> groff, CVS    : adding the .ig section kills the left margin

As mentioned by Keith, interpolating undefined registers within .ig
actually defines them (with value zero).  Consequently, the line

  .if !rPO .nr PO \\n(.o

from s.tmac (in macro address@hidden') no longer initializes \n[PO] as
expected.

Looking into the `tmac/s' file from Solaris I see that the start-up
code *always* sets PO.  Since groff allows the setting of `PO' on the
command line, this is not an option for groff.


    Werner