mdocml: Below DIAGNOSTICS, document the SYSERR message level; jmc@

mdocml: Below DIAGNOSTICS, document the SYSERR message level; jmc@

[schwarze]

Log Message:
-----------
Below DIAGNOSTICS, document the SYSERR message level;
jmc@ wondered what it meant and agrees with this patch.

Modified Files:
--------------
    mdocml:
        mandoc.1

Revision Data
-------------
Index: mandoc.1
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/mandoc.1,v
retrieving revision 1.104
retrieving revision 1.105
diff -Lmandoc.1 -Lmandoc.1 -u -p -r1.104 -r1.105
--- mandoc.1
+++ mandoc.1
@@ -1,7 +1,7 @@
 .\"	$Id$
 .\"
 .\" Copyright (c) 2009, 2010, 2011 Kristaps Dzonsons <kristaps@bsd.lv>
-.\" Copyright (c) 2012 Ingo Schwarze <schwarze@openbsd.org>
+.\" Copyright (c) 2012, 2014 Ingo Schwarze <schwarze@openbsd.org>
 .\"
 .\" Permission to use, copy, modify, and distribute this software for any
 .\" purpose with or without fee is hereby granted, provided that the above
@@ -524,6 +524,9 @@ fields are omitted when meaningless.
 .Pp
 Message levels have the following meanings:
 .Bl -tag -width "warning"
+.It Cm syserr
+Opening or reading an input file failed, so the parser cannot
+even be started and no output is produced from that input file.
 .It Cm fatal
 The parser is unable to parse a given input file at all.
 No formatted output is produced from that input file.
@@ -559,8 +562,7 @@ output mode.
 The
 .Nm
 utility may also print messages related to invalid command line arguments
-or operating system errors, for example when memory is exhausted or
-input files cannot be read.
+or operating system errors, for example when memory is exhausted.
 Such messages may not carry the prefix described above.
 .Sh COMPATIBILITY
 This section summarises
--
 To unsubscribe send an email to source+unsubscribe@mdocml.bsd.lv