Below DIAGNOSTICS, document the SYSERR message level;

jmc@ wondered what it meant and agrees with this patch.

1 files changed, 5 insertions, 3 deletions

diff --git a/mandoc.1 b/mandoc.1
index c8b7aa47..2530851c 100644
--- a/mandoc.1
+++ b/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