Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #14342

Re: Issue – Invalid command documented – BASH_BUILTINS(1) –

From Ricky Tigg <ricky.tigg@gmail.com>
Newsgroups gnu.bash.bug
Subject Re: Issue – Invalid command documented – BASH_BUILTINS(1) –
Date 2018-07-14 19:57 +0200
Message-ID <mailman.3587.1531591060.1292.bug-bash@gnu.org> (permalink)
References <CAM_8-CirY1trFh32NPBkZ6TzsB2Ai9tzk25zp2Jz_ehUJsa8cw@mail.gmail.com>

Show all headers | View raw


That's what I indeed observed; since 'BASH_BUILTINS(1)' is documented here
written in the conventional syntax; then at least it tends to indicate that its
respective command 'man 1 bash_builtins' can be executed in Bash. Maybe
then there is an hidden reason for which it should be considered according
to another way,.

2018-07-14 16:38 GMT+02:00 Ricky Tigg <ricky.tigg@gmail.com>:

> OS: Fedora; Component: bash.x86_64 4.4.23-1.fc28 @updates
>
> Description: Non-valid documented command 'BASH_BUILTINS(1)'.
>
> $ man 1 bash_builtins
> No manual entry for bash_builtins in section 1
> $ man bash_builtins
> No manual entry for bash_builtins
>
> Additional informations:
> $ apropos bash
> (...)
> alias (1)            - bash built-in commands, see bash(1)
> (...)
>
> $ man alias
> BASH_BUILTINS(1)                                         General Commands
> Manual                                        BASH_BUILTINS(1)
>
> NAME
>        bash, :, ., [, alias, (...), wait - bash built-in commands, see
> bash(1)
>
>

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread


Thread

Re: Issue – Invalid command documented – BASH_BUILTINS(1) – Ricky Tigg <ricky.tigg@gmail.com> - 2018-07-14 19:57 +0200

csiph-web