From 7582daff204d17b170462dc6b7f6fd218be6afc9 Mon Sep 17 00:00:00 2001 From: Ingo Schwarze Date: Sat, 25 Aug 2018 16:53:38 +0000 Subject: 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? --- regress/roff/char/badarg.out_ascii | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 regress/roff/char/badarg.out_ascii (limited to 'regress/roff/char/badarg.out_ascii') 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) -- cgit