Great, thanks. Then that isn't the source of my problem: x.troff:11: fatal error: input stack limit exceeded (probable infinite loop)
But I just figured it out: ms requires .TL before anything else (and after .RP). The way I have the code starts with something that is not .TL. And thus, the above error. :-( I guess I'll just give a .RP, then a .TL, then an .AU, then the rest of the doc. Nick Stoughton wrote: > > On Thu, 2007-08-02 at 16:44 -0700, andlabs wrote: >> Hello. I'm working with code that amends to ms' PP. The code uses a >> number >> register 1t - that is the number 1 followed by lowercase t. First, is >> such >> an identifier legal in groff? Second, what happens if a register is not >> defined with .nr and used with \n(xx - would it be 0 or would it be an >> error? > > Yes and 0! It took all of about 15 seconds to test: > > $ nroff << END > .nr a 1 > .nr 1t 2 > this is the value of a: \na and this is the value of b: \nb. Did you see > it? > and this is the value of 1t: \n[1t] > END > > produces > > this is the value of a: 1 and this is the value of b: 0. Did you > see it? and this is the value of 1t: 2 > -- > Nick > > > > > -- View this message in context: http://www.nabble.com/Number-registers-tf4209781.html#a11975323 Sent from the Groff - General mailing list archive at Nabble.com.
