Hi Berny, As I mentioned in the other thread, this patch fixes 'make syntax-check' with an updated Gnulib.
All the failures were because of a newly added sc_codespell rule. Collin
>From 3dd848dedc36d06aa18eaa5fb32580e3a657c63e Mon Sep 17 00:00:00 2001 Message-ID: <3dd848dedc36d06aa18eaa5fb32580e3a657c63e.1752110868.git.collin.fu...@gmail.com> From: Collin Funk <[email protected]> Date: Wed, 9 Jul 2025 18:21:26 -0700 Subject: [PATCH] maint: ensure that new "make syntax-check"-run sc_codespell passes * cfg.mk (codespell_ignore_words_list): Ignore false-positives. (exclude_file_name_regexp--sc_codespell): Skip some file names. * NEWS: Fix typos. * README-hacking: Likewise. * doc/find-maint.texi: Likewise. * doc/find.texi: Likewise. * bootstrap.conf: Fix typos in comments. * find/ftsfind.c: Likewise. * find/parser.c: Likewise. * find/print.c: Likewise. * find/testsuite/find.gnu/exec-one-rtn-fail.exp: Likewise. * find/testsuite/find.posix/bracket-depth.exp: Likewise. * find/testsuite/find.posix/exec-nogaps.exp: Likewise. * find/testsuite/find.posix/files-not-expressions1.exp: Likewise. * find/testsuite/find.posix/files-not-expressions2.exp: Likewise. * find/testsuite/find.posix/files-not-expressions3.exp: Likewise. * find/util.c: Likewise. * init.cfg: Likewise. * lib/regextype.h: Likewise. * lib/splitstring.h: Likewise. * locate/locate.c: Likewise. * locate/updatedb.sh: Likewise. * tests/find/exec-plus-last-file.sh: Likewise. * tests/find/files0-from.sh: Likewise. * tests/xargs/test-sigusr.c: Likewise. * tests/xargs/verbose-quote.sh: Likewise. * xargs/xargs.c: Likewise. --- NEWS | 30 +++++++++---------- README-hacking | 2 +- bootstrap.conf | 2 +- cfg.mk | 7 +++++ doc/find-maint.texi | 8 ++--- doc/find.texi | 4 +-- find/ftsfind.c | 2 +- find/parser.c | 4 +-- find/print.c | 4 +-- find/testsuite/find.gnu/exec-one-rtn-fail.exp | 2 +- find/testsuite/find.posix/bracket-depth.exp | 2 +- find/testsuite/find.posix/exec-nogaps.exp | 2 +- .../find.posix/files-not-expressions1.exp | 2 +- .../find.posix/files-not-expressions2.exp | 2 +- .../find.posix/files-not-expressions3.exp | 2 +- find/util.c | 2 +- init.cfg | 2 +- lib/regextype.h | 2 +- lib/splitstring.h | 2 +- locate/locate.c | 4 +-- locate/updatedb.sh | 4 +-- tests/find/exec-plus-last-file.sh | 2 +- tests/find/files0-from.sh | 4 +-- tests/xargs/test-sigusr.c | 2 +- tests/xargs/verbose-quote.sh | 2 +- xargs/xargs.c | 2 +- 26 files changed, 55 insertions(+), 48 deletions(-) diff --git a/NEWS b/NEWS index 9d9472db..06fe48e7 100644 --- a/NEWS +++ b/NEWS @@ -515,7 +515,7 @@ posix-egrep. This is the result of a change to gnulib to bring it into line with GNU grep (see https://debbugs.gnu.org/20974#22). ** Translations -Updated translations: Estonian, Swedish, Polish, Vietnamese, Ukranian, +Updated translations: Estonian, Swedish, Polish, Vietnamese, Ukrainian, Norwegian Bokmaal, Czech, Russian, French, Hungarian. ** Bug Fixes: @@ -544,7 +544,7 @@ Norwegian Bokmaal, Czech, Russian, French, Hungarian. #45062: Enabling CACHE_IDS causes segfaults (this bug affects many historic releases, probably since release 3.0 in 1991). You would not have been affected by this problem unless you used - the option --enable-id-cache when invoking confgure. + the option --enable-id-cache when invoking configure. #42903: checklists.py now supports Python 3. @@ -592,7 +592,7 @@ Some minor documentation improvements are listed in "Bug Fixes" below. ** Translations -Updated translations: Estonian, Polish, Ukranian. +Updated translations: Estonian, Polish, Ukrainian. * Major changes in release 4.5.12, 2013-09-22 @@ -691,7 +691,7 @@ For example use "xargs /bin/echo < foo" rather than "xargs < foo". A new option is provided, --process-slot-var. If you set this, xargs will set the indicated environment variable in each child. The values -are re-used, but no executing child process will have the same value +are reused, but no executing child process will have the same value as another executing child process. This wishlist item was Savannah bug #29512. @@ -721,7 +721,7 @@ expression types selected by the -regextype option have slightly changed, to bring them into line with the behaviour of the GNU C library. For "awk", character classes (such as [[:digit:]]) are now supported. For "gnu-awk" and "posix-awk", intervals are supported and -invalid interval specifcations are treated as literals (for example +invalid interval specifications are treated as literals (for example 'a{1' is treated as 'a\{1'). @@ -804,7 +804,7 @@ Updated Vietnamese, Czech, Dutch, Polish, Russian translations. ** Performance changes -If you use the -fstype FOO predicate and specify a filsystem type FOO +If you use the -fstype FOO predicate and specify a filesystem type FOO which is not known (e.g. present in /etc/mtab) at the time find starts, that predicate is now equivalent to -false. This substitution currently occurs at optimisation level 2 and above. @@ -880,7 +880,7 @@ in the text). #22708: Exit status 126 and 127 from the utility invoked from xargs now makes xargs return 123, meaning that exit status values 126 and -127 now unambigously mean that the utility could not be run or could +127 now unambiguously mean that the utility could not be run or could not be found, respectively. ** Documentation Changes @@ -920,13 +920,13 @@ unknown user or is missing. #25154: Allow compilation with C compilers that don't allow declarations to follow statements. -#24342: -inum predicate shoud use dirent.d_ino instead of stat.st_ino +#24342: -inum predicate should use dirent.d_ino instead of stat.st_ino (this is a performance bug). ** Translations Updated translations for Bulgarian, German, Irish, Hungarian, -Lithuanian, Dutch, Polish, Slovenian, Swedish, Turkish, Ukranian, +Lithuanian, Dutch, Polish, Slovenian, Swedish, Turkish, Ukrainian, Vietnamese. ** Documentation Changes @@ -944,7 +944,7 @@ The file README-CVS has been renamed to README-hacking and improved. Changes to gnulib's fts code should provide performance improvements in find when processing very large directories (for example directories containing significantly more than 10000 filenames). -Performance imporvements may only exist for some find command lines +Performance improvements may only exist for some find command lines (performance testing was done for the fts implementation itself but we haven't done the analogous performance tests in find). @@ -1407,7 +1407,7 @@ servers. #11668: FreeBSD extensions for time specification are now implemented. In fact, these were included in findutils-4.3.3. The -change was listed as a functional change (whcih it is) and this bug +change was listed as a functional change (which it is) and this bug report was not mentioned. ** Documentation Fixes @@ -1632,7 +1632,7 @@ problem was worse for -exec. Savannah bug #16579: Updatedb now works if it is running as a user whose login shell is not actually a shell. -There have also been a number of documentation improvements (includng +There have also been a number of documentation improvements (including Savannah bug #16269). ** Functional changes @@ -1952,7 +1952,7 @@ Some typos in the manual pages have been fixed. Various parts of the manual now point out that it is good practice to quote the argument of "-name". The manpage now has a "NON-BUGS" section which explains some symptoms that look like bugs but aren't. The explanations of the "%k" -and "%b" directives to "find -printf" have been imrpoved. +and "%b" directives to "find -printf" have been improved. * Major changes in release 4.2.21, 2005-06-07 @@ -2168,7 +2168,7 @@ New Vietnamese message translation. have it. *** Bugfix to the findutils 4.2.6 automount handling (which hadn't been enabled on Solaris). -*** Reenabled internationalisation support (which had been accidentally +*** Re-enabled internationalisation support (which had been accidentally disabled in findutils-4.2.5). * Major changes in release 4.2.6, 2004-11-21 @@ -2206,7 +2206,7 @@ New Vietnamese message translation. *** If you specify a 'find' option after non-option, a warning message is now issued. Options should be specified immediately after the list of paths to search. These warnings are enabled if you - specify the -warn option, or if stdin is a tty. They are diabled + specify the -warn option, or if stdin is a tty. They are disabled by the use of the -nowarn option. *** Like find, the locate program now supports an option --null (short form -0) which changes the result separator from newline to NULL. diff --git a/README-hacking b/README-hacking index c76c5530..0777bb9d 100644 --- a/README-hacking +++ b/README-hacking @@ -106,7 +106,7 @@ proc_max. MAX_PROC_MAX. --- example ends --- -There are several things to notice about this checkin message. Most +There are several things to notice about this check-in message. Most importantly, it begins with a single line summary of the whole change. This needs to be short. It would be used as the subject line of patches mailed by "git send-email". Some people begin that line with diff --git a/bootstrap.conf b/bootstrap.conf index 15eac866..9cdeb0d0 100644 --- a/bootstrap.conf +++ b/bootstrap.conf @@ -55,7 +55,7 @@ gendocs # consider using gendocs # consider using sig2str in xargs # consider using signal (why not: maybe we don't need those features) -# consider using the dev-ino moduile to support -samefile. +# consider using the dev-ino module to support -samefile. # consider removing stpcpy # We have rpmatch, either use it for -ok and xargs or remove the dependency diff --git a/cfg.mk b/cfg.mk index 4de155ae..fcac6b5c 100644 --- a/cfg.mk +++ b/cfg.mk @@ -96,6 +96,13 @@ exclude_file_name_regexp--sc_bindtextdomain = \ exclude_file_name_regexp--sc_unmarked_diagnostics = \ ^(tests/xargs/test-sigusr)\.c$$ +# Things that 'codespell' mistakenly flags as typos. +codespell_ignore_words_list = afile,bu,debbugs,filll,fo,hel,ois,siz,ublic,TE, + +# Files to exclude from sc_codespell +exclude_file_name_regexp--sc_codespell = \ + ^(THANKS|build-aux/git-log-fix)$$ + # sc_prohibit_strcmp is broken because it gives false positives for # cases where neither argument is a string literal. local-checks-to-skip += sc_prohibit_strcmp diff --git a/doc/find-maint.texi b/doc/find-maint.texi index 4ad8b7a0..0c47056a 100644 --- a/doc/find-maint.texi +++ b/doc/find-maint.texi @@ -87,7 +87,7 @@ @node Introduction also a recent document, so there will be a many areas in which improvements can be made. If you find that the document misses out important information or any part of the document is be so terse as to -be unuseful, please ask for help on the @email{bug-findutils@@gnu.org} +be useless, please ask for help on the @email{bug-findutils@@gnu.org} mailing list. We'll try to improve this document too. @@ -537,7 +537,7 @@ @node Using the GNU Portability Library directory you checked out earlier. Observe that your test now passes. @item Prepare a Gnulib patch In the gnulib subdirectory, use @code{git format-patch} to prepare the -patch. Follow the normal usage for checkin comments (take a look at +patch. Follow the normal usage for check-in comments (take a look at the output of @code{git log}). Check that the patch conforms with the GNU coding standards, and email it to the Gnulib mailing list. @item Wait for the patch to be applied @@ -674,7 +674,7 @@ @node Documentation to answer the questions ``what changed?'' and ``why was it changed?''. The file is generated from the git commit messages during @code{make dist}. If a change fixes a bug, always give the bug reference number in the -@file{NEWS} file and of course also in the checkin message. +@file{NEWS} file and of course also in the check-in message. In general, it should be possible to enumerate all material changes to a function by searching for its name in @file{ChangeLog}. Mention when each release is made. @@ -947,7 +947,7 @@ @node Security The GNU project discovered the problem while 'locate' was being worked on; this is the first public announcement of the problem. -The GNU findutils mantainer has issued a patch as part of this +The GNU findutils maintainer has issued a patch as part of this announcement. The patch appears below. A source release of findutils-4.2.31 will be issued on 2007-05-30. diff --git a/doc/find.texi b/doc/find.texi index c84d8a4a..8da85307 100644 --- a/doc/find.texi +++ b/doc/find.texi @@ -2872,7 +2872,7 @@ @node Controlling Parallelism heavily loaded). Whether or not parallel execution will work well for you depends on -the nature of the commmand you are running in parallel, on the +the nature of the command you are running in parallel, on the configuration of the system on which you are running the command, and on the other work being done on the system at the time. @@ -3568,7 +3568,7 @@ @node Optimisation Options types are returned by @code{readdir()} and so these predicates are faster to evaluate than predicates which need to stat the file first. -If you use the @samp{-fstype FOO} predicate and specify a filsystem +If you use the @samp{-fstype FOO} predicate and specify a filesystem type @samp{FOO} which is not known (that is, present in @file{/etc/mtab}) at the time @code{find} starts, that predicate is equivalent to @samp{-false}. diff --git a/find/ftsfind.c b/find/ftsfind.c index c5f721ec..90e16008 100644 --- a/find/ftsfind.c +++ b/find/ftsfind.c @@ -618,7 +618,7 @@ process_all_startpoints (int argc, char *argv[]) { if (!argv_starting_points) { - /* If no starting points are given on the comman line, then + /* If no starting points are given on the command line, then * fall back to processing the current directory, i.e., ".". * We use a temporary variable here because some actions modify * the path temporarily. Hence if we use a string constant, diff --git a/find/parser.c b/find/parser.c index 5f447933..bd18df60 100644 --- a/find/parser.c +++ b/find/parser.c @@ -2170,7 +2170,7 @@ parse_samefile (const struct parser_table* entry, char **argv, int *arg_ptr) return false; set_stat_placeholders (&fst); - /* POSIX systems are free to re-use the inode number of a deleted + /* POSIX systems are free to reuse the inode number of a deleted * file. To ensure that we are not fooled by inode reuse, we hold * the file open if we can. This would prevent the system reusing * the file. @@ -3056,7 +3056,7 @@ get_relative_timestamp (const char *str, assert (nanosec < nanosec_per_sec); /* Perform the subtraction, and then check for overflow. - * On systems where signed aritmetic overflow does not + * On systems where signed arithmetic overflow does not * wrap, this check may be unreliable. The C standard * does not require this approach to work, but I am aware * of no platforms where it fails. diff --git a/find/print.c b/find/print.c index 04d638d4..30360a0a 100644 --- a/find/print.c +++ b/find/print.c @@ -588,7 +588,7 @@ format_date (struct timespec ts, int kind) * For example, some systems return junk in the tv_nsec part of * st_birthtime. An example of this is the NetBSD-4.0-RELENG kernel * (at Sat Mar 24 18:46:46 2007) running a NetBSD-3.1-RELEASE - * runtime and examining files on an msdos filesytem. So for that + * runtime and examining files on an msdos filesystem. So for that * reason we set NS_BUF_LEN to 32, which is simply "long enough" as * opposed to "exactly the right size". Note that the behaviour of * NetBSD appears to be a result of the use of uninitialized data, @@ -698,7 +698,7 @@ format_date (struct timespec ts, int kind) *--p = '-'; /* XXX: Ugh, relying on internal details of human_readable(). */ /* Add the nanoseconds part. Because we cannot enforce a - * particlar implementation of human_readable, we cannot assume + * particular implementation of human_readable, we cannot assume * any particular value for (p-buf). So we need to be careful * that there is enough space remaining in the buffer. */ diff --git a/find/testsuite/find.gnu/exec-one-rtn-fail.exp b/find/testsuite/find.gnu/exec-one-rtn-fail.exp index b761d1d3..4d0e7f2e 100644 --- a/find/testsuite/find.gnu/exec-one-rtn-fail.exp +++ b/find/testsuite/find.gnu/exec-one-rtn-fail.exp @@ -1,4 +1,4 @@ # If -exec \; fails, it should return false. The return -# value of find should stil; be 0, unless another error has +# value of find should still be 0, unless another error has # happened. find_start p { /tmp -exec false \; -o \( -printf "yep\n" -quit \) } diff --git a/find/testsuite/find.posix/bracket-depth.exp b/find/testsuite/find.posix/bracket-depth.exp index 8ebadcdd..2a9b5734 100644 --- a/find/testsuite/find.posix/bracket-depth.exp +++ b/find/testsuite/find.posix/bracket-depth.exp @@ -1,4 +1,4 @@ exec rm -rf tmp exec mkdir tmp -# shoud not result in a fatal error. +# should not result in a fatal error. find_start p { tmp \( -depth \) -false -print } diff --git a/find/testsuite/find.posix/exec-nogaps.exp b/find/testsuite/find.posix/exec-nogaps.exp index 108a7a15..11f22f11 100644 --- a/find/testsuite/find.posix/exec-nogaps.exp +++ b/find/testsuite/find.posix/exec-nogaps.exp @@ -21,7 +21,7 @@ for f; do echo "$f"; done close $script exec chmod 0500 tmp/list.sh -send_log "creeating files $file_list\n" +send_log "creating files $file_list\n" foreach filename $file_list { } diff --git a/find/testsuite/find.posix/files-not-expressions1.exp b/find/testsuite/find.posix/files-not-expressions1.exp index b54ff8ca..629cf667 100644 --- a/find/testsuite/find.posix/files-not-expressions1.exp +++ b/find/testsuite/find.posix/files-not-expressions1.exp @@ -2,7 +2,7 @@ set files "\(1 " foreach file $files { touch $file } -# shoud not result in a fatal error. +# should not result in a fatal error. find_start p { \(1 } foreach file $files { file delete -- $file } diff --git a/find/testsuite/find.posix/files-not-expressions2.exp b/find/testsuite/find.posix/files-not-expressions2.exp index b699a24f..0bd564fb 100644 --- a/find/testsuite/find.posix/files-not-expressions2.exp +++ b/find/testsuite/find.posix/files-not-expressions2.exp @@ -2,7 +2,7 @@ set files "!2" foreach file $files { touch $file } -# shoud not result in a fatal error. +# should not result in a fatal error. find_start p { !2 } foreach file $files { file delete -- $file } diff --git a/find/testsuite/find.posix/files-not-expressions3.exp b/find/testsuite/find.posix/files-not-expressions3.exp index 96749e04..ddad7c56 100644 --- a/find/testsuite/find.posix/files-not-expressions3.exp +++ b/find/testsuite/find.posix/files-not-expressions3.exp @@ -2,7 +2,7 @@ set files "\)" foreach file $files { touch $file } -# shoud not result in a fatal error. +# should not result in a fatal error. find_start p { \) } foreach file $files { file delete -- $file } diff --git a/find/util.c b/find/util.c index b22e6e7b..4a9d8c26 100644 --- a/find/util.c +++ b/find/util.c @@ -969,7 +969,7 @@ set_option_defaults (struct options *p) p->posixly_correct = false; /* We call check_nofollow() before setlocale() because the numbers - * for which we check (in the results of uname) definitiely have "." + * for which we check (in the results of uname) definitely have "." * as the decimal point indicator even under locales for which that * is not normally true. Hence atof would do the wrong thing * if we call it after setlocale(). diff --git a/init.cfg b/init.cfg index 4b9e01f5..0d89e666 100644 --- a/init.cfg +++ b/init.cfg @@ -560,7 +560,7 @@ require_sparse_support_() # Compile a shared lib using the GCC options for doing so. # Pass input and output file as parameters respectively. -# Any other optional parmeters are passed to $CC. +# Any other optional parameters are passed to $CC. gcc_shared_() { local in=$1 diff --git a/lib/regextype.h b/lib/regextype.h index 552e3893..c7294044 100644 --- a/lib/regextype.h +++ b/lib/regextype.h @@ -40,7 +40,7 @@ enum { const char * get_regex_type_name(unsigned int ix); -/* Returns the option mask name corresponding to regular expresion +/* Returns the option mask name corresponding to regular expression * type index IX. Indexes start at 0. Behaviour is undefined if IX * has a value which would cause get_regex_type_name to return NULL. */ diff --git a/lib/splitstring.h b/lib/splitstring.h index 19d9ee39..324e3dad 100644 --- a/lib/splitstring.h +++ b/lib/splitstring.h @@ -23,7 +23,7 @@ /* Split a string into fields. The string is never modified. * * A false return value indicates that there are no more fields. - * Otherwise the next field is at the poisition indicated by *POS and + * Otherwise the next field is at the position indicated by *POS and * has length *LEN. * * Set FIRST to true only on the first call for any given value of s. diff --git a/locate/locate.c b/locate/locate.c index a1575e80..9b67e0bb 100644 --- a/locate/locate.c +++ b/locate/locate.c @@ -35,7 +35,7 @@ 8, No 1, February/March, 1983, p. 8. However, latterly code changes to provide additional functionality - became dificult to make with the existing reading scheme, and so + became difficult to make with the existing reading scheme, and so we no longer perform the matching as efficiently as we used to (that is, we no longer use the same algorithm). @@ -1033,7 +1033,7 @@ search_one_database (int argc, * We ensure that we can return to the previous behaviour * by using two variables, do_check_existence (which we act on) * and check_existence (which indicates the default before we - * adjust it on the bassis of what kind of database we;re using + * adjust it on the basis of what kind of database we're using */ do_check_existence = check_existence; diff --git a/locate/updatedb.sh b/locate/updatedb.sh index 0469d0ea..cb4109e6 100644 --- a/locate/updatedb.sh +++ b/locate/updatedb.sh @@ -39,7 +39,7 @@ Written by Eric B. Decker, James Youngman, and Kevin Dalley. # character encoding errors in text-based tools like "sort". To avoid # this, we set LC_ALL=C. This will, presumably, not work perfectly on # systems where LC_ALL is not the way to do locale configuration or -# some other seting can override this. +# some other setting can override this. LC_ALL=C export LC_ALL @@ -147,7 +147,7 @@ select_shell() { # Any global options for find? : ${FINDOPTIONS=} -# What shell shoud we use? We should use a POSIX-ish sh. +# What shell should we use? We should use a POSIX-ish sh. : ${SHELL="/bin/sh"} # Non-network directories to put in the database. diff --git a/tests/find/exec-plus-last-file.sh b/tests/find/exec-plus-last-file.sh index c99c417c..39d62084 100755 --- a/tests/find/exec-plus-last-file.sh +++ b/tests/find/exec-plus-last-file.sh @@ -1,6 +1,6 @@ #!/bin/sh # This test verifies that find invokes the given command for the -# multiple-argument sytax '-exec CMD {} +'. Between FINDUTILS-4.2.12 +# multiple-argument syntax '-exec CMD {} +'. Between FINDUTILS-4.2.12 # and v4.6.0, find(1) would have failed to execute CMD another time # if there was only one last single file argument. # See Savannah bug #48030. diff --git a/tests/find/files0-from.sh b/tests/find/files0-from.sh index 429fda3e..d7ae9a10 100755 --- a/tests/find/files0-from.sh +++ b/tests/find/files0-from.sh @@ -90,8 +90,8 @@ fi # Exercise a directory argument. # On most modern systems like GNU/Linux, read(2)-ing from a directory file -# descriptor will fail with EISDIR. Skip on other plaforms where that succeeds, -# e.g. on GNU/Hurd and AIX. +# descriptor will fail with EISDIR. Skip on other platforms where that +# succeeds, e.g. on GNU/Hurd and AIX. if returns_ 1 cat / >/dev/null; then returns_ 1 find -files0-from / > out 2> err \ && grep 'read error' err \ diff --git a/tests/xargs/test-sigusr.c b/tests/xargs/test-sigusr.c index 81687501..648dd9ef 100644 --- a/tests/xargs/test-sigusr.c +++ b/tests/xargs/test-sigusr.c @@ -215,7 +215,7 @@ run_xargs(const char *option, const char *opt_arg, int send_signal) close(pipefd[1]); /* close write end */ if (read(pipefd[0], &child_errno, sizeof child_errno) < sizeof child_errno) { - /* The exec succeded in the child, and its write end of the pipe was closed. */ + /* The exec succeeded in the child, and its write end of the pipe was closed. */ } else { diff --git a/tests/xargs/verbose-quote.sh b/tests/xargs/verbose-quote.sh index ba0bf145..1b34c54f 100755 --- a/tests/xargs/verbose-quote.sh +++ b/tests/xargs/verbose-quote.sh @@ -27,7 +27,7 @@ printf "%s\n" \ && chmod +x 'my command' \ || framework_failure_ -# Run xargs with -t for verious commands which require quoting. +# Run xargs with -t for various commands which require quoting. # (Use NL because dash as /bin/sh does not know $'\n' syntax.) nl=' ' diff --git a/xargs/xargs.c b/xargs/xargs.c index 517f963c..6af333aa 100644 --- a/xargs/xargs.c +++ b/xargs/xargs.c @@ -201,7 +201,7 @@ enum XargsStatusValues { XARGS_EXIT_CLIENT_EXIT_NONZERO = 123, /* utility exited with nonzero status */ XARGS_EXIT_CLIENT_EXIT_255 = 124, /* utility exited with status 255 */ XARGS_EXIT_CLIENT_FATAL_SIG = 125, /* utility died from a fatal signal */ - XARGS_EXIT_COMMAND_CANNOT_BE_RUN = 126, /* canot run the command */ + XARGS_EXIT_COMMAND_CANNOT_BE_RUN = 126, /* cannot run the command */ XARGS_EXIT_COMMAND_NOT_FOUND = 127, /* cannot find the command */ }; /* Exit status values the child might use. */ -- 2.50.0
