On 2013-09-27 20:19, Roland Winkler wrote:
> Yet I think that the info pages are supposed to provide the definitive
> information about GNU software. So I still believe that it would be
> useful to list these builtins in the info pages, too. Certainly,
> the info pages are more useful for getting
On Fri Sep 27 2013 Greg Wooledge wrote:
> $ help true
> true: true
> Return a successful result.
>
> Exit Status:
> Always succeeds.
> $ help false
> false: false
> Return an unsuccessful result.
>
> Exit Status:
> Always fails.
Thanks, I did not know that.
Yet I
On Fri, Sep 27, 2013 at 03:50:09PM +0530, Roland Winkler wrote:
> I guess there is not too much one can say about the bash built-ins
> `true' and `false'. Nonetheless, I suggest that the info pages
> should list these built-ins individually like other built-ins.
> Currently, the only hint on their
I guess there is not too much one can say about the bash built-ins
`true' and `false'. Nonetheless, I suggest that the info pages
should list these built-ins individually like other built-ins.
Currently, the only hint on their existence is buried in the info
node on Shell Builtin Commands saying t
I'm writing a completion where, in some cases, I'd like to use
COMPREPLY=() to indicate that no more arguments to a command are
expected, but in other cases, I'd like to offer the default Readline
behavior for filename completions.
So, if I have a directory 'foo', I'd like the shell to first compl
