.nr weirdness

["Anthony J. Bentley" <anthony@cathet.us>]

From sbcl(1):

.nr step 1 1
.IP \n[step]. 3
Debugger is disabled, if requested.
.IP \n+[step].
Any system initialization file is loaded, unless prohibited.
.IP \n+[step].
Any user initialization file is loaded, unless prohibited.
.IP \n+[step].
\-\-eval and \-\-load options are processed in the order given.

Here is the diff between mandoc and groff output:


-       -1.
-          Debugger is disabled, if requested.
+       1. Debugger is disabled, if requested.

-       0[step].
-          Any system initialization file is loaded, unless prohibited.
+       2. Any system initialization file is loaded, unless prohibited.

-       0[step].
-          Any user initialization file is loaded, unless prohibited.
+       3. Any user initialization file is loaded, unless prohibited.

-       0[step].
-          --eval and --load options are processed in the order given.
+       4. --eval and --load options are processed in the order given.


Here's my superficial analysis of the (distinct?) problems here:

- step is initialized to -1 instead of 1. This seems to be due to the
extra argument in ".nr step 1 1" (roff(7) only describes .nr as taking
two arguments, and if I take off the last one, it gets initialized
properly).

- step should be incremented but it isn't. From quick testing it seems
that the printed value of "\n+[step]" is always 0 no matter what is in
step.

- In mandoc, there's a newline after the ".IP \n+[step]." gets output.
Groff doesn't print one.

That's all for now...

-- 
Anthony J. Bentley
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv