Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15012
| From | Peng Yu <pengyu.ut@gmail.com> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: bug in dirname loadable? |
| Date | 2018-12-30 17:42 -0600 |
| Message-ID | <mailman.6596.1546213385.1284.bug-bash@gnu.org> (permalink) |
| References | <CABrM6wmOxFYgi=aH5b4sSCVBSDQN54hp98hmhPrRKL3Swm0HHg@mail.gmail.com> <1c578205-822b-aa22-def1-16c05e4bb1bc@case.edu> |
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
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: bug in dirname loadable? Peng Yu <pengyu.ut@gmail.com> - 2018-12-30 17:42 -0600
csiph-web