diff options
| author | Ingo Schwarze <schwarze@openbsd.org> | 2015-01-14 22:02:49 +0000 |
|---|---|---|
| committer | Ingo Schwarze <schwarze@openbsd.org> | 2015-01-14 22:02:49 +0000 |
| commit | d278d189880b66efa26e74464c25442317de546f (patch) | |
| tree | 6c6e0c720ed13f43d774e52a894b7365085c3172 /mandoc.1 | |
| parent | b4dc7abb73518820b5be9949b77b4bca86da3c42 (diff) | |
| download | mandoc-d278d189880b66efa26e74464c25442317de546f.tar.gz | |
To get rid of SYSERR entries in enum mandocerr, downgrade problems with
missing and unreadable files from SYSERR to ERROR.
Needed for upcoming work.
As a bonus, this minimally simplifies code and documentation.
Diffstat (limited to 'mandoc.1')
| -rw-r--r-- | mandoc.1 | 18 |
1 files changed, 11 insertions, 7 deletions
@@ -1,7 +1,7 @@ .\" $Id$ .\" .\" Copyright (c) 2009, 2010, 2011 Kristaps Dzonsons <kristaps@bsd.lv> -.\" Copyright (c) 2012, 2014 Ingo Schwarze <schwarze@openbsd.org> +.\" Copyright (c) 2012, 2014, 2015 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 @@ -543,8 +543,8 @@ A fatal parsing error occurred. Invalid command line arguments were specified. No input files have been read. .It 6 -An operating system error occurred, for example memory exhaustion or an -error accessing input files. +An operating system error occurred, for example exhaustion +of memory, file descriptors, or process table entries. Such errors cause .Nm to exit at once, possibly in the middle of parsing or formatting a file. @@ -603,9 +603,6 @@ fields. .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. @@ -619,6 +616,12 @@ the parser is able to continue, and the error does not prevent generation of formatted output, but typically, preparing that output involves information loss, broken document structure or unintended formatting. +.Pp +Non-existent or unreadable input files are also reported on the +.Cm error +level. +In that case, the parser cannot even be started and no output +is produced from those input files. .It Cm warning An input file uses obsolete, discouraged or non-portable syntax. All the same, the meaning of the input is unambiguous and a correct @@ -632,7 +635,8 @@ Messages of the .Cm warning and .Cm error -levels are hidden unless their level, or a lower level, is requested using a +levels except those about non-existent or unreadable input files +are hidden unless their level, or a lower level, is requested using a .Fl W option or .Fl T Ns Cm lint |