-
-
Notifications
You must be signed in to change notification settings - Fork 285
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
g.copy: Report failed copy using an error message (#1086)
Changes in behavior: 1. Non-zero return code (EXIT_FAILURE) has now also a corresponding error message (ERROR:) not just warning messages (from do_copy.c). 2. Skipping an input as ineligible for copying may now result in an error (fatal error with EXIT_FAILURE). The error newly occurs when all inputs are skipped or, most importantly, when only one input was provided and it was skipped. The skipping (in main.c) is now consistently reported as skipping. The warning messages also contain more details and the new error messages point to them. The M_do_copy function (do_copy.c) now starts with 'Copying' because it is at the begining of the process instead of 'Copy' which is misleading (is the user supposed to copy). The user manual has now a new intro and newly describes the behavior on error discussing the much simpler single input case separately. Documentation mentions g.mapset -p and g.mapsets -p instead of mentioning outdated `$MAPSET` and assuming that it is clear what mapset search path is. Co-authored-by: Stefan Blumentrath <stefan.blumentrath@gmx.de>
- Loading branch information
1 parent
47e52ec
commit 39868ea
Showing
3 changed files
with
70 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters