From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: In terminal output of man(7) documents, stop printing two extra
Date: Mon, 28 Jun 2021 14:50:45 -0500 (EST) [thread overview]
Message-ID: <c2aa06651c895d4b@mandoc.bsd.lv> (raw)
Log Message:
-----------
In terminal output of man(7) documents, stop printing two extra blank
lines before the NAME section and before the page footer. While these
blank lines had a long tradition, they didn't really serve any purpose
and merely wasted screen real estate. Besides, this makes output from
man(7) more similar to output from mdoc(7).
This commit keeps mandoc compatible with groff-current,
where G. Branden Robinson committed the same change
on June 16 (groff commit 2278d6ed).
Modified Files:
--------------
mandoc:
TODO
man_term.c
mandoc.1
Revision Data
-------------
Index: mandoc.1
===================================================================
RCS file: /home/cvs/mandoc/mandoc/mandoc.1,v
retrieving revision 1.250
retrieving revision 1.251
diff -Lmandoc.1 -Lmandoc.1 -u -p -r1.250 -r1.251
--- mandoc.1
+++ mandoc.1
@@ -301,8 +301,8 @@ Format
input files in
.Xr mdoc 7
output style.
-Specifically, this suppresses the two additional blank lines near the
-top and the bottom of each page, and it implies
+This prints the operating system name rather than the page title
+on the right side of the footer line, and it implies
.Fl O Cm indent Ns =5 .
One useful application is for checking that
.Fl T Cm man
Index: man_term.c
===================================================================
RCS file: /home/cvs/mandoc/mandoc/man_term.c,v
retrieving revision 1.235
retrieving revision 1.236
diff -Lman_term.c -Lman_term.c -u -p -r1.235 -r1.236
--- man_term.c
+++ man_term.c
@@ -1021,10 +1021,6 @@ print_man_foot(struct termp *p, const st
*/
if ( ! p->mdocstyle) {
- if (meta->hasbody) {
- term_vspace(p);
- term_vspace(p);
- }
mandoc_asprintf(&title, "%s(%s)",
meta->title, meta->msec);
} else if (meta->os != NULL) {
@@ -1143,9 +1139,5 @@ print_man_head(struct termp *p, const st
*/
term_vspace(p);
- if ( ! p->mdocstyle) {
- term_vspace(p);
- term_vspace(p);
- }
free(title);
}
Index: TODO
===================================================================
RCS file: /home/cvs/mandoc/mandoc/TODO,v
retrieving revision 1.315
retrieving revision 1.316
diff -LTODO -LTODO -u -p -r1.315 -r1.316
--- TODO
+++ TODO
@@ -456,7 +456,7 @@ are mere guesses, and some may be wrong.
- HTML formatting of .nf should avoid <br/>
and not close and re-open <pre> on .P
- my mail to ports@ 27 Jun 2021 16:09:20 +0200
+ Reuben ua Brig 27 Jun 2021 17:26:29 +1000
loc ** exist ** algo * size * imp **
- get rid of the last handful of style= attributes such that
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2021-06-28 19:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c2aa06651c895d4b@mandoc.bsd.lv \
--to=schwarze@mandoc.bsd.lv \
--cc=source@mandoc.bsd.lv \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).