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

2012-04-18 Thread Victor Engmark
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 > > ) > > > > Running simply `builtin` prints nothing and ret

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

2012-04-18 Thread Chet Ramey
On 4/18/12 9:18 AM, Victor Engmark wrote: > (Re-posted from Stack Overflow > ) > > Running simply `builtin` prints nothing and returns exit code 0. This is in > accordance with `help builtin`, which shows

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

2012-04-18 Thread Victor Engmark
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?

2012-04-18 Thread Victor Engmark
(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-