Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: Peng Yu <pengyu.ut@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Re: bug in dirname loadable?
Date: Sun, 30 Dec 2018 17:42:50 -0600
Lines: 28
Approved: bug-bash@gnu.org
Message-ID: <mailman.6596.1546213385.1284.bug-bash@gnu.org>
References: <CABrM6wmOxFYgi=aH5b4sSCVBSDQN54hp98hmhPrRKL3Swm0HHg@mail.gmail.com> <1c578205-822b-aa22-def1-16c05e4bb1bc@case.edu>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Cc: bug-bash <bug-bash@gnu.org>
To: Chester Ramey <chet.ramey@case.edu>
Envelope-to: bug-bash@gnu.org
In-Reply-To: <1c578205-822b-aa22-def1-16c05e4bb1bc@case.edu>
Precedence: list
Xref: csiph.com gnu.bash.bug:15012

On Wed, Dec 26, 2018 at 11:35 AM Chet Ramey <chet.ramey@case.edu> wrote:
>
> On 12/24/18 10:35 PM, Peng Yu wrote:
> > dirname loadable gives the following error. I think the coreutils'
> > direname's convention is better. Should it be considered as a bug to
> > fix?
> >
> > $ dirname -- -a
> > dirname: usage: dirname string
> > $(type -P dirname) -- -a
> > .
>
> Yes, dirname should skip over a `--' denoting the end of options. Thanks
> for the report.

There is a similar problem in `basename`. Is it due to a common bug on
how loadables are programmed?

$ builtin basename -a
-bash: basename: -a: invalid option
basename: usage: basename string [suffix]
$ builtin basename -- -a
--

-- 
Regards,
Peng