From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: Some more tests of no-fill mode similar to mdoc/Bd/blank.in
Date: Mon, 15 Aug 2022 14:00:10 -0500 (EST) [thread overview]
Message-ID: <336a1eb4bfd255cd@mandoc.bsd.lv> (raw)
Log Message:
-----------
Some more tests of no-fill mode similar to mdoc/Bd/blank.in
after vertical spacing was improved in man_term.c rev. 1.239.
Modified Files:
--------------
mandoc/regress/man/nf:
indent.in
indent.out_ascii
Revision Data
-------------
Index: indent.out_ascii
===================================================================
RCS file: /home/cvs/mandoc/mandoc/regress/man/nf/indent.out_ascii,v
retrieving revision 1.2
retrieving revision 1.3
diff -Lregress/man/nf/indent.out_ascii -Lregress/man/nf/indent.out_ascii -u -p -r1.2 -r1.3
--- regress/man/nf/indent.out_ascii
+++ regress/man/nf/indent.out_ascii
@@ -9,13 +9,22 @@ D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
two words
and three words
This is a very long line; because it is indented, it is a bit too long to fit.
- blank line:
+ completely blank line:
- line with only a zero-width space:
+ line containing a blank character:
- line with only a normal space character:
+ line containing two blank characters:
+ line containing space tab space:
+
+ line containing a zero-width space:
+
+ line containing an invalid numbered character escape:
+
+ line containing an invalid named character escape:
+
+ line containing a font escape:
end of literal
He is some more regular text.
-OpenBSD January 4, 2011 NF-INDENT(1)
+OpenBSD August 15, 2022 NF-INDENT(1)
Index: indent.in
===================================================================
RCS file: /home/cvs/mandoc/mandoc/regress/man/nf/indent.in,v
retrieving revision 1.2
retrieving revision 1.3
diff -Lregress/man/nf/indent.in -Lregress/man/nf/indent.in -u -p -r1.2 -r1.3
--- regress/man/nf/indent.in
+++ regress/man/nf/indent.in
@@ -1,5 +1,5 @@
-.\" $OpenBSD: indent.in,v 1.4 2017/07/04 14:53:24 schwarze Exp $
-.TH NF-INDENT 1 "January 4, 2011"
+.\" $OpenBSD: indent.in,v 1.5 2022/08/15 18:55:29 schwarze Exp $
+.TH NF-INDENT 1 "August 15, 2022"
.SH NAME
nf-indent \- indentation of literal blocks
.SH DESCRIPTION
@@ -10,12 +10,22 @@ oneword
two words
and three words
This is a very long line; because it is indented, it is a bit too long to fit.
-blank line:
+completely blank line:
-line with only a zero-width space:
+line containing a blank character:
+
+line containing two blank characters:
+
+line containing space tab space:
+
+line containing a zero-width space:
\&
-line with only a normal space character:
-
+line containing an invalid numbered character escape:
+\N'257'
+line containing an invalid named character escape:
+\[foobar]
+line containing a font escape:
+\fR
end of literal
.fi
He is some more
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2022-08-15 19:00 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=336a1eb4bfd255cd@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).