summaryrefslogtreecommitdiffstats
path: root/regress/roff/char/badarg.out_ascii
diff options
context:
space:
mode:
authorIngo Schwarze <schwarze@openbsd.org>2018-08-25 16:53:38 +0000
committerIngo Schwarze <schwarze@openbsd.org>2018-08-25 16:53:38 +0000
commit7582daff204d17b170462dc6b7f6fd218be6afc9 (patch)
treeff78b1959cd4fa9d7a802eb91fa11f10dc2f9e1e /regress/roff/char/badarg.out_ascii
parent4208da29a6d83d71a70576139d86e6a306290132 (diff)
downloadmandoc-7582daff204d17b170462dc6b7f6fd218be6afc9.tar.gz
Rudimentary implementation of the roff(7) .char (output glyph
definition) request, used for example by groff_hdtbl(7). This simplistic implementation may interact incorrectly with the .tr (input character translation) request. But come on, you are not only using .char *and* .tr, but you do so with respect to the same character in the same manual page?
Diffstat (limited to 'regress/roff/char/badarg.out_ascii')
-rw-r--r--regress/roff/char/badarg.out_ascii13
1 files changed, 13 insertions, 0 deletions
diff --git a/regress/roff/char/badarg.out_ascii b/regress/roff/char/badarg.out_ascii
new file mode 100644
index 00000000..287479a8
--- /dev/null
+++ b/regress/roff/char/badarg.out_ascii
@@ -0,0 +1,13 @@
+CHAR-BADARG(1) General Commands Manual CHAR-BADARG(1)
+
+
+
+NNAAMMEE
+ char-badarg - char requests with invalid arguments
+
+DDEESSCCRRIIPPTTIIOONN
+ myc: <> x
+
+
+
+OpenBSD August 25, 2018 CHAR-BADARG(1)