[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] exit(3) Value of nmh Commands.

From: Ken Hornstein
Subject: Re: [Nmh-workers] exit(3) Value of nmh Commands.
Date: Sun, 27 Aug 2017 13:22:50 -0400

>mhparam(1) deviates.
>        mhparam returns the number of components that were not found,
>        but limits the return value to 120 to avoid ambiguity, e.g. 127
>        is used by shells to indicate ‘command not found', and 256 would
>        wrap to 0, falsely indicating success.

Huh, I never saw that before.  If no one depends on that (I would find
it unlikely, but hey, I've been surprised by the behavior of nmh users
before!) then I say get rid of that behavior and make it behave like
everything else.

>I'd like to switch mhparam to the normal 0 or 1 that Unix commands
>generally follow.  After all, rm(1) doesn't attempt to return a tally of
>files it couldn't remove.  Does this need advance notice in 1.8's NEWS
>so it can only happen in 1.9.  IOW, is anyone likely to be depending on

Assuming no one objects, I think it can be done for 1.8.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]