Follow-up Comment #8, bug #63777 (project groff):
How about this?
I overran my vee, which kicked an example to the next page, but oh well.
I reduced the comprehensiveness of my parameter list, since as noted in
comment #7, the anatomies of lines and pages haven't been presented yet.
diff --git a/doc/groff.texi b/doc/groff.texi
index 3bd029003..17369a045 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -7878,15 +7878,20 @@ Indicator of output device selection (Boolean-valued);
see
@cindex @code{sp} request, causing implicit break
@cindex @code{ti} request, causing implicit break
@cindex @code{trf} request, causing implicit break
-A break updates the drawing position per the page offset, indentation,
-vertical spacing, and page length, interrupting filling. Various ways
-of causing breaks were shown in @ref{Breaking}. The @code{br} request
-likewise causes a break. A break is implied by several other
-requests:@: @code{bp}, @code{ce}, @code{cf}, @code{fi}, @code{fl},
+When an output line is pending, a break moves the drawing position to
+the beginning of the next text baseline, interrupting
+filling.@footnote{If the vertical drawing position is negative---as it
+is when the formatter starts up---a break starts a new page unless an
+end-of-input macro is being interpreted. @xref{End-of-input Traps}.}
+Various ways of causing breaks were shown in @ref{Breaking}. The
+@code{br} request likewise causes a break. Several other requests imply
+breaks:@: @code{bp}, @code{ce}, @code{cf}, @code{fi}, @code{fl},
@code{in}, @code{nf}, @code{rj}, @code{sp}, @code{ti}, and @code{trf}.
If the no-break control character is used with any of these requests,
GNU @code{troff} suppresses the break; instead the requested operation
-takes effect at the next break. @samp{'br} does nothing.
+takes effect at the next break. @samp{'br} does nothing. If no output
+line is pending, a break does not normally alter the drawing position;
+but any other effects of a breaking request still occur.
@Example
.ll 55n
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?63777>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
