On Tue Jun 21 08:09:46 2005, [EMAIL PROTECTED] wrote: > > > > 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. > > > > So this would lead to the rule "don't mention PO before the -ms > > macros kick in, unless you intend to set it"? Seems like a fairly > > acceptable and predictable rule to me -- despite my earlier > > confusion. > > Yes. Can provide a patch for groff_ms.man to document that?
I can try ... here's one that I'm not very happy with; it may or may not be acceptable to you. My terminology may be off: "undefined", "evaluate", "document" and, uh, "she". /Jörgen Index: tmac/groff_ms.man =================================================================== RCS file: /cvsroot/groff/groff/tmac/groff_ms.man,v retrieving revision 1.16 diff -u -r1.16 groff_ms.man --- tmac/groff_ms.man 23 Sep 2004 11:54:25 -0000 1.16 +++ tmac/groff_ms.man 21 Jun 2005 07:14:17 -0000 @@ -1338,6 +1338,19 @@ or .I "groff ms" should use this number register. +. +.IP \(bu +For +.I "groff ms" +to use the default page offset (left margin), +the +.B PO +number register must be undefined when the first +.B ms +macro is encountered. +This implies that the user may not evaluate +.B PO +early in the document, unless she also intends to change it. .br .ne 23 . -- // Jörgen Grahn "Koka lopplummer, bada Ross, loppor borta." \X/ <[EMAIL PROTECTED]> -- Jonas _______________________________________________ Groff mailing list Groff@gnu.org http://lists.gnu.org/mailman/listinfo/groff
