Re: Shouldn't "type" and "command" complain if there are no parameters?

On Thu, Apr 26, 2012 at 3:50 AM, Linda Walsh wrote: > Victor Engmark wrote: > >> Re-post from <http://unix.stackexchange.**com/questions/36752/why-are-** >> parameters-to-bashs-command-**and-type-optional<http://unix.stackexchange.com/questions/36752/why-are-parameters-t

Re: Why are parameters to Bash's builtin optional?

On Fri, Apr 20, 2012 at 9:18 PM, Chet Ramey wrote: > On 4/18/12 11:27 AM, Victor Engmark wrote: >>>  I can see printing a list of builtins, though `enable' already does that. >> >> I guess the difference would be that `builtin` prints *all* builtins, and >> *ne

Re: Why are parameters to Bash's builtin optional?

On Wednesday, April 18, 2012 4:36:36 PM UTC+2, Chet Ramey wrote: > On 4/18/12 9:18 AM, Victor Engmark wrote: > > (Re-posted from Stack Overflow > > <http://unix.stackexchange.com/questions/36751/why-are-parameters-to-bashs-builtin-optional>) > > > > Running si

Shouldn't "type" and "command" complain if there are no parameters?

Re-post from : [T]hese commands print nothing and return exit code 0 if no parameters are provided. But [...] `help command` and `help type` both state that at least one parameter is mandatory.

Why are parameters to Bash's builtin optional?

(Re-posted from Stack Overflow ) Running simply `builtin` prints nothing and returns exit code 0. This is in accordance with `help builtin`, which shows all parameters as optional. But why isn't this no-