Be simpler and more consistent about reporting I/O errors.
authorPaul Eggert <eggert@cs.ucla.edu>
Tue, 16 Jul 2013 18:30:52 +0000 (11:30 -0700)
committerPaul Eggert <eggert@cs.ucla.edu>
Tue, 16 Jul 2013 18:30:52 +0000 (11:30 -0700)
commit4e604a5d70c4f26abe8bb3494346c598389906b3
tree6842a74fd23245cde0e5e4a97aa42ca32c119a0f
parenta9757f6a03cce5ff2931b1125a9a2249573c8e1c
Be simpler and more consistent about reporting I/O errors.

* fileio.c (Fcopy_file, Finsert_file_contents, Fwrite_region):
Say "Read error" and "Write error", rather than "I/O error", or
"IO error reading", or "IO error writing", when a read or write
error occurs.
* process.c (Fmake_network_process, wait_reading_process_output)
(send_process, Fprocess_send_eof, wait_reading_process_output):
Capitalize diagnostics consistently.  Put "failed foo" at the
start of the diagnostic, so that we don't capitalize the
function name "foo".  Consistently say "failed" for such
diagnostics.
* sysdep.c, w32.c (serial_open): Now accepts Lisp string, not C string.
All callers changed.  This is so it can use report_file_error.
* sysdep.c (serial_open, serial_configure): Capitalize I/O
diagnostics consistently as above.
src/ChangeLog
src/fileio.c
src/process.c
src/sysdep.c
src/systty.h
src/w32.c