Re: Worth mentioning in documentation

2017-06-24 Thread Pádraig Brady
On 10/08/15 05:55, Eric Blake wrote: > On 08/10/2015 02:18 AM, Juanma wrote: > >> Here is another point I find confusing: I thought a "shell builtin" didn't >> have a separate binary executable file, like 'cd' (which cd => fail), > > Actually, POSIX requires that there be a separate 'cd' binary,

Re: Worth mentioning in documentation

2015-08-11 Thread Juanma
El Mon 10 of Aug, Bob Proulx profirió estas palabras: > [...] This is why quoting as if they were external programs is > required. On the other hand [[ has always been a builtin and > therefore the shell can avoid one layer of quoting and does. That's a good point to make. Thanks for clarifying.

Re: Worth mentioning in documentation

2015-08-10 Thread Bob Proulx
Greg Wooledge wrote: > Juanma wrote: > > > [ is an ordinary command (a "shell builtin") > > > > Here is another point I find confusing: I thought a "shell builtin" didn't > > have a separate binary executable file, like 'cd' (which cd => fail), but > > some of them do have such form (which [ => /u

Re: Worth mentioning in documentation

2015-08-10 Thread Eric Blake
On 08/10/2015 02:18 AM, Juanma wrote: > Here is another point I find confusing: I thought a "shell builtin" didn't > have a separate binary executable file, like 'cd' (which cd => fail), Actually, POSIX requires that there be a separate 'cd' binary, although it does not have to behave the same a

Re: Worth mentioning in documentation

2015-08-10 Thread Greg Wooledge
On Mon, Aug 10, 2015 at 10:18:52AM +0200, Juanma wrote: > > [ is an ordinary command (a "shell builtin") > > Here is another point I find confusing: I thought a "shell builtin" didn't > have a separate binary executable file, like 'cd' (which cd => fail), but > some of them do have such form (whic

Re: Worth mentioning in documentation

2015-08-10 Thread Juanma
El Fri 7 of Aug, Greg Wooledge profirió estas palabras: > > Those brackets I cited above: ( expression ) > In the US we call those "parentheses", and we reserve the word "brackets" > (or "square brackets") for [ ]. I realize that the UK uses different > terminology. Hence, the word is ambiguous a

Re: Worth mentioning in documentation

2015-08-07 Thread Eduardo A . Bustamante López
> In the US we call those "parentheses", and we reserve the word "brackets" > (or "square brackets") for [ ]. I realize that the UK uses different > terminology. Hence, the word is ambiguous and you should always type > the actual characters you mean. These are also "paréntesis" in Spanish, so it

Re: Worth mentioning in documentation

2015-08-07 Thread Greg Wooledge
On Fri, Aug 07, 2015 at 10:00:53AM +0200, Juanma wrote: > El Thu 6 of Aug, Greg Wooledge profirió estas palabras: > > I believe you are talking about the section that discusses the [[ ... ]] > > command. > > Yes, you are right. And I mean, concretely, the last part: > | Expressions may be combined

Re: Worth mentioning in documentation

2015-08-06 Thread Greg Wooledge
On Thu, Aug 06, 2015 at 04:13:30PM +0200, Juanma wrote: > In section ???3.2.4.2 Conditional Constructs??? of Bash docs (both in > ???man??? and in the web), at the end, there is an explanation on combining > expressions, starting with the use of brackets. > > There it would be worth to mention t

Worth mentioning in documentation

2015-08-06 Thread Juanma
Hello. In section “3.2.4.2 Conditional Constructs” of Bash docs (both in ‘man’ and in the web), at the end, there is an explanation on combining expressions, starting with the use of brackets. There it would be worth to mention that: 1. you must escape the brackets, also inside script files 2.