and the symbol @code{error}. Occasionally it includes additional
symbols, which are intermediate classifications, narrower than
@code{error} but broader than a single error symbol. For example, all
-the errors in accessing files have the condition @code{file-error}.
+the errors in accessing files have the condition @code{file-error}. If
+we do not say here that a certain error symbol has additional error
+conditions, that means it has none.
As a special exception, the error symbol @code{quit} does not have the
condition @code{error}, because quitting is not considered an error.
@code{"Buffer is read-only"}@*
@xref{Read Only Buffers}.
+@item coding-system-error
+@code{"Invalid coding system"}@*
+@xref{Coding Systems}.
+
+@item cyclic-function-indirection
+@code{"Symbol's chain of function indirections\@* contains a loop"}@*
+@xref{Function Indirection}.
+
@item end-of-buffer
@code{"End of buffer"}@*
@xref{Motion}.
@item end-of-file
@code{"End of file during parsing"}@*
-This is not a @code{file-error}.@*
+Note that this is not a subcategory of @code{file-error},
+because it pertains to the Lisp reader, not to file I/O.
@xref{Input Functions}.
+@item file-already-exists
+This is a subcategory of @code{file-error}.@*
+@xref{Writing to Files}.
+
+@item file-date-error
+This is a subcategory of @code{file-error}. It occurs when
+@code{copy-file} tries and fails to set the last-modification time of
+the output file. @xref{Changing Files}.
+
@item file-error
This error and its subcategories do not have error-strings, because the
error message is constructed from the data items alone when the error
@xref{Files}.
@item file-locked
-This is a @code{file-error}.@*
+This is a subcategory of @code{file-error}.@*
@xref{File Locks}.
-@item file-already-exists
-This is a @code{file-error}.@*
-@xref{Writing to Files}.
-
@item file-supersession
-This is a @code{file-error}.@*
+This is a subcategory of @code{file-error}.@*
@xref{Modification Time}.
+@item ftp-error
+This is a subcategory of @code{file-error}, which results from problems
+in accessing a remote file using ftp.@*
+@xref{Remote Files,,, emacs, The Emacs Manual}.
+
@item invalid-function
@code{"Invalid function"}@*
@xref{Classifying Lists}.
@code{"Invalid regexp"}@*
@xref{Regular Expressions}.
+@item mark-inactive
+@code{"Mark inactive"}@*
+@xref{The Mark}.
+
@item no-catch
@code{"No catch for tag"}@*
@xref{Catch and Throw}.
+@item scan-error
+@code{"Scan error"}@*
+This happens when certain syntax-parsing functions
+find invalid syntax or mismatched parentheses.@*
+@xref{List Motion}, and @ref{Parsing Expressions}.
+
@item search-failed
@code{"Search failed"}@*
@xref{Searching and Matching}.
@item setting-constant
@code{"Attempt to set a constant symbol"}@*
-The values of the symbols @code{nil} and @code{t}
+The values of the symbols @code{nil} and @code{t},
+and any symbols that start with @samp{:},
may not be changed.@*
@xref{Constant Variables, , Variables that Never Change}.
+@item text-read-only
+@code{"Text is read-only"}@*
+@xref{Special Properties}.
+
+@item undefined-color
+@code{"Undefined color"}@*
+@xref{Color Names}.
+
@item void-function
@code{"Symbol's function definition is void"}@*
@xref{Function Cells}.
@item wrong-type-argument
@code{"Wrong type argument"}@*
@xref{Type Predicates}.
+@end table
+
+ These kinds of error, which are classified as special cases of
+@code{arith-error}, can occur on certain systems for invalid use of
+mathematical functions.
+
+@table @code
+@item domain-error
+@code{"Arithmetic domain error"}@*
+@xref{Math Functions}.
+
+@item overflow-error
+@code{"Arithmetic overflow error"}@*
+@xref{Math Functions}.
+
+@item range-error
+@code{"Arithmetic range error"}@*
+@xref{Math Functions}.
+
+@item singularity-error
+@code{"Arithmetic singularity error"}@*
+@xref{Math Functions}.
+
+@item underflow-error
+@code{"Arithmetic underflow error"}@*
+@xref{Math Functions}.
@end table
HCoop / bpt / emacs.git / blobdiff