bug-bash
[Top][All Lists]
Advanced

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

Re: builtin_name --help


From: Andreas Kähäri
Subject: Re: builtin_name --help
Date: Fri, 19 Sep 2025 17:26:58 +0200

On Fri, Sep 19, 2025 at 05:00:12PM +0200, pourko--- via Bug reports for the GNU 
Bourne Again SHell wrote:
> I don't know how else to say it. My question has nothing to do 
> with "documentation". I am talking about any command that recognizes
> "--help" as a valid option, nothing else. (See my original post.)

It was I who brought up documentation.  Why should a utility exit with
a zero exit status when an *undocumented* option is used?  It doesn't
matter how "expected to be supported" the option is.  If it's not
documented, it's not expected to be supported.  Using it currently
does the right thing when it exits with a non-zero exit status (the
superfluous output that a utility produces with "--help" is a separate
issue).

> 
> Sep 19, 2025, 09:51 by chet.ramey@case.edu:
> 
> > On 9/19/25 10:46 AM, pourko--- via Bug reports for the GNU Bourne Again 
> > SHell wrote:
> >
> >>> So this is the bug report? That the builtins that accept --help (some
> >>> builtins are documented as not accepting any options) do not return 0?
> >>>
> >>
> >> No, it most certainly is not.
> >>
> >
> > And yet you say it is below:
> >
> >> To rephrase my original posting: Commands that do support "--help", they 
> >> usually
> >> exit with return code 0. Wouldn't it be more reasonable if our builtins 
> >> behaved
> >> the same way?
> >>
> >
> >
> >
> >
> >
> >
> > -- 
> > ``The lyf so short, the craft so long to lerne.'' - Chaucer
> >  ``Ars longa, vita brevis'' - Hippocrates
> > Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/
> >

-- 
Matti Andreas Kähäri
Uppsala, Sweden

.



reply via email to

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