CVS log for mandoc/regress/roff/cond/close.out_lint

[BACK] Up to [cvsweb.bsd.lv] / mandoc / regress / roff / cond

Request diff between arbitrary revisions


Default branch: MAIN
Current tag: MAIN


Revision 1.8 / (download) - annotate - [select for diffs], Mon Aug 3 11:02:58 2020 UTC (3 years, 10 months ago) by schwarze
Branch: MAIN
CVS Tags: VERSION_1_14_6, HEAD
Changes since 1.7: +3 -2 lines
Diff to previous 1.7 (colored)

Put the code handling \} into a new function roff_cond_checkend()
and call that function not only from both places where copies
existed - when processing text lines and when processing request/macro
lines in conditional block scope - but also when closing a macro
definition request, such that this construction works:

.if n \{.de macroname
macro content
.. \} ignored arguments
.macroname

This fixes a bug reported by John Gardner <gardnerjohng at gmail dot com>.

While here, avoid a confusing decrement of the line scope counter
in roffnode_cleanscope() for conditional blocks that do not have
line scope in the first place (no functional change for this part).
Also improve validation of an internal invariant in roff_cblock()
and polish some comments.

Revision 1.7 / (download) - annotate - [select for diffs], Mon Nov 26 17:44:34 2018 UTC (5 years, 6 months ago) by schwarze
Branch: MAIN
CVS Tags: VERSION_1_14_5
Changes since 1.6: +2 -2 lines
Diff to previous 1.6 (colored)

When a conditional block is closed by putting "\}" on a text line
by itself (which is somewhat unusual but not invalid; most authors
use the empty macro line ".\}" instead), agree more closely with
groff and do not produce a double space in the output.

Quirk reported by millert@.

While here, tweak the rest of the function body of roff_cond_text()
to more closely match roff_cond_sub().  The subtly different handling
could make people (including myself) wonder whether there is any
point in being different.  Testing shows there is not.

Revision 1.6 / (download) - annotate - [select for diffs], Tue Jul 4 15:26:31 2017 UTC (6 years, 11 months ago) by schwarze
Branch: MAIN
CVS Tags: VERSION_1_14_4, VERSION_1_14_3, VERSION_1_14_2
Changes since 1.5: +2 -3 lines
Diff to previous 1.5 (colored)

Messages of the -Wbase level now print STYLE:.  Since this
causes horrible churn anyway, profit of the opportunity to stop
excessive testing, such that this is hopefully the last instance
of such churn.  Consistently use OpenBSD RCS tags, blank .Os,
blank fourth .TH argument, and Mdocdate like everywhere else.
Use -Ios=OpenBSD for platform-independent predictable output.

Revision 1.5 / (download) - annotate - [select for diffs], Sun Jun 25 12:53:31 2017 UTC (6 years, 11 months ago) by schwarze
Branch: MAIN
Changes since 1.4: +1 -1 lines
Diff to previous 1.4 (colored)

cope with changes in BASE messages

Revision 1.4 / (download) - annotate - [select for diffs], Sat Jun 17 22:45:26 2017 UTC (7 years ago) by schwarze
Branch: MAIN
Changes since 1.3: +1 -0 lines
Diff to previous 1.3 (colored)

style message about missing RCS ids; inspired by mdoclint

Revision 1.3 / (download) - annotate - [select for diffs], Fri May 5 15:17:36 2017 UTC (7 years, 1 month ago) by schwarze
Branch: MAIN
Changes since 1.2: +1 -0 lines
Diff to previous 1.2 (colored)

Move .sp to the roff modules.  Enough infrastructure is in place
now that this actually saves code: -70 LOC.

Revision 1.2 / (download) - annotate - [select for diffs], Thu May 4 17:48:35 2017 UTC (7 years, 1 month ago) by schwarze
Branch: MAIN
Changes since 1.1: +1 -1 lines
Diff to previous 1.1 (colored)

Parser reorg:
Generate the first node on the roff level: .br
Fix some column numbers in diagnostic messages while here.

Revision 1.1 / (download) - annotate - [select for diffs], Wed Feb 8 03:03:19 2017 UTC (7 years, 4 months ago) by schwarze
Branch: MAIN
CVS Tags: VERSION_1_14_1, VERSION_1_13

Finally port the OpenBSD regression suite.
Both kristaps@ and wiz@ repeated asked for this,
literally for years.

This form allows you to request diff's between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.




CVSweb