Follow-up Comment #20, bug #65474 (group groff):
I confess that I still don't know how .ie and .el work, despite the attempts
in the documentation (and in this bug report) to explain them. For example,
given the following test of nesting .ie and .el two deep (in .MX) and three
deep (in .MY):
.pl 1
.de MX
\\$1 \\$2
.ie \\$1 \{\
. ie \\$2 a
. el b
.\}
.el \{\
. ie \\$2 c
. el d
.\}
z
.br
..
.MX 1 1
.MX 1 0
.MX 0 1
.MX 0 0
.de MY
\\$1 \\$2 \\$3
.ie \\$1 \{\
. ie \\$2 \{\
. ie \\$3 A
. el B
. \}
. el \{\
. ie \\$3 C
. el D
.\}
.el \{\
. ie \\$2 \{\
. ie \\$3 E
. el F
. \}
. el \{\
. ie \\$3 G
. el H
. \}
.\}
Z
.br
..
.MY 1 1 1
.MY 1 1 0
.MY 1 0 1
.MY 1 0 0
.MY 0 1 1
.MY 0 1 0
.MY 0 0 1
.MY 0 0 0
groff -Tascii -ww and Solaris 10 nroff both output the following without any
warnings on groff's part:
1 1 a z
1 0 b z
0 1 c z
0 0 d z
1 1 1 A Z
1 1 0 B Z
1 0 1 C Z
1 0 0 D Z
0 1 1
I can't explain why .MX's two levels of .ie/.el work, whereas .MY's three
levels do not work; can anyone else explain it? If so, it'd be helpful if the
explanation were in the manual.
I am starting to think that man pages should never use .ie as that might
simplify portability.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65474>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
