bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #61973] [me] delayed text doesn't use annotation vertical spacing


From: G. Branden Robinson
Subject: [bug #61973] [me] delayed text doesn't use annotation vertical spacing
Date: Tue, 1 Feb 2022 08:03:04 -0500 (EST)

URL:
  <https://savannah.gnu.org/bugs/?61973>

                 Summary: [me] delayed text doesn't use annotation vertical
spacing
                 Project: GNU troff
            Submitted by: gbranden
            Submitted on: Tue 01 Feb 2022 01:03:02 PM UTC
                Category: Macro me
                Severity: 3 - Normal
              Item Group: Incorrect behaviour
                  Status: In Progress
                 Privacy: Public
             Assigned to: gbranden
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None

    _______________________________________________________

Details:

Delayed text is supposed to receive the vertical spacing of
other annotations.

Quoting _meref.me_ from groff 1.22.4, at which point it hadn't
changed much in 30 years.


.sh 1 Annotations
.TL
.b .(d
.DE
Begin delayed text.
Everything in the next keep
is saved for output
later with
.b .pd ,
in a manner
similar to footnotes.
.TL
.b .)d
.i n
.DE
End delayed text.
The delayed text number register
.NR ($d
and the associated string
.ST #
are incremented if
.ST #
has been referenced.
.TL
.b .pd
.DE
Print delayed text.
Everything diverted via
.b .(d
is printed and truncated.
This might be used
at the end of each chapter.

The line spacing as a percentage of the pointsize expressed in units
is stored in
.NR ($v .
The percentage used internally
by displays and annotations
is stored in
.NR ($V
(although this is not used by
.b .sz ).


Given the following input, we would therefore expect the delayed
text items to be single-spaced, not double-spaced like the main
matter.

(We assign directly to `$v` and `$V`.  These are _groff_
extensions.  See bug #61710 for more on these matters.)


.nr $v 240 \" double-space most text
.nr $V 120 \" single-space displays and annotations
.uh "A demonstration of vertical spacing with delayed text"
.lp
In our exploration of computing science fundamentals,
we shall consider the authoritative sources
(\*#
.(d
\*# Knuth 1983.
Sed ut perspiciatis, unde omnis iste natus error sit voluptatem
accusantium doloremque laudantium, totam rem aperiam eaque ipsa, quae ab
illo inventore veritatis et quasi architecto beatae vitae dicta sunt,
explicabo.
.)d
\*#,
.(d
\*# Floyd 1993.
Nemo enim ipsam voluptatem, quia voluptas sit, aspernatur
aut odit aut fugit, sed quia consequuntur magni dolores eos, qui ratione
voluptatem sequi nesciunt, neque porro quisquam est, qui dolorem ipsum,
quia dolor sit amet consectetur adipiscivelit, sed quia non-numquam eius
modi tempora incidunt, ut labore et dolore magnam aliquam quaerat
voluptatem.
.)d
\*#)
.(d
\*# Curry 1963.
Ut enim ad minima veniam, quis nostrum exercitationem ullam
corporis suscipitlaboriosam, nisi ut aliquid ex ea commodi consequatur?
.)d
as well as another,
more dubious,
one\*#.
.(d
\*# Torvalds 2001.
Quis autem vel eum iure reprehenderit, qui inea voluptate velit esse,
quam nihil molestiae consequatur, vel illum, qui dolorem eum fugiat, quo
voluptas nulla pariatur?
.)d
.uh "References"
.pd


See attached screenshot, which shows output before and after a
2-line fix I have in preparation.

It seems likely to me that the older behavior was an oversight
on Allman's part; apart from the package's behavior
contradicting its reference manual (which he also wrote) on this
point, the inclusion of `\n(bs` space between each delayed text
item suggests to me that the spacing _within_ those delayed text
items is expected to be single (ordinarily).

I admit I'm relying on surmise, but I have been unable to find
any model me(7) documents in Web searches apart from the ones we
distribute, or earlier versions thereof.

Maybe someone can help with that.





    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61973>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]